Exec command in App Engine Peoplecode stopped working in PT8.49.10 ??

Question

We run an a few app engine jobs that use the Exec command in peoplecode
to call a bat file which moves a file from one directory to another (a backup directory).
It had been working fine but since we upgraded to PT8.49.10, from PT8.47 the job abends
at the Exec command with the following message:
'Exec function error: (2,181) WC_FUNCLIB_HR.WC_FILENAME_IN.FieldFormula Name:wcBackupFile
PCPC:799 Statement:9
Called from:WCAPP001.MAIN.GBL.default.1900-01-01.Step03.OnExecute Statement:4 .'
The actual statement it is abending on within the wcBackupFile function is this:
&processid = Exec(&cmdstr, &synch);
When re-creating the problem in our test environment I can see that:
&cmdstr = "C:\temp\wcapp001.bat"
&synch = False
C:\temp\wcapp001.bat =
cmd /c move /y \\dom_wfld\dfsroot\hr\files\req.csv \\dom_wfld\dfsroot\hr\bkup\req_20090318_112338.csv
The command will work if I paste the contents of the bat file into a command line
but it abends when called from the app engine program with the 8.49.10 tools.
We are a DB2 shop.
If anyone has some ideas regarding this I'd certainly welcome them.
Thanks,

Answer 1

Well, I figured out what the issue was and I appreciate everyone's suggestions made in this thread. The problem was that we actually changed our folder configuration when we went to PT8.49.10 (I know, a pretty big clue I didn't divulge in earlier posts) so now PS_HOME was a little different than before. The Exec command, if using boolean parameters (which we were) instead of Exec_constant + Path_Constant parameters, appends the PS_HOME value to the beginning of the path to the bat file. With the change in our folder structure the Exec command was not able to actually find the bat file to execute it. I made the change to using the Exec command, as follows, and it seems to be working fine. Here's what I changed it to: &processid = Exec(&cmdstr, %Exec_Synchronous + %FilePath_Absolute);
Again, thanks for your suggestions.