I had a number of unsuccessful attempts to get interactive processes
to run in background on NT (ADSM schedules among them).  The usual
error message suggested a missing file but helpfully omitted the name
of the file.  It turned out that the missing file was the console
screen for stdout/stderror messages.

Two possible solutions (I found the first one first and tend to use it
because of the logging benefits):
1.      run your command with redirection of output to a temporary file
(see Daniel's example below),
2.      run your command under the "CMD shell" with the /C flag (e.g.,
POSTCommand=CMD /C JP_POST.BAT)

Hope it helps,
Murray Nicholas
Systems Specialist
HALTEK PTY LTD