That won't work as the batch script build step runs in a seperate process to the ant build step and therefore enviroment variables are not retained between different build steps.
The solution is to use the envInject plugin [1], and have the batch script output the parameters to a properties file.
e.g.
batch script
echo 'param="Went there - didnt like it"' > env.properties
#append other properties to file as needed
Inject enviroment variables
set "Properties File Path" to env.properties
then your Ant build step
where the param shold be avaliable in the same way that the build parameters are.
Chris