This is kind of a "do nothing" that I wrote to try and test what I'm trying to accomplish. I'm trying to figure a way to pass the process number to the job (the bat file)
The cdp file:
/*BEGIN_REQUESTER_COMMENTS
$PNODE$="ATLTECH04" $PNODE_OS$="Windows"
$OPTIONS$="WDOS"
END_REQUESTER_COMMENTS*/
LCLCOPY PROCESS
&PNUMVAR=$PNUMBER$
COPYSTEP
RUN JOB PNODE (DSN=wINDOWS)
SYSOPTS="pgm(D:\P\LOCALCOPY.BAT) args(D:\MIKEG\INCOMING D:\MYTEMP\INCOMING &PNUMVAR)"
PEND
The contents of the bat file:
COPY %1 %2.%3
Bottom line is, once I can figure out how to do it, I'm just trying to copy a trigger file called INCOMING from one directory to another one, and add an extension to the file name, which would be the process number that ran successfully on Direct Connect. The process above is what I'm playing with to try and figure out how to pass that process number along. | [reply] [Watch: Dir/Any] |
jmiklg:
In that case, then you'd just pass the process number in the args list, and then your batch file could get it. For example, given this as the batch file:
@echo off
rem
rem do_nothing.bat <SrcDir> <DstDir> <ProcID>
rem
echo Source Dir: '%1' >D:\MYTEMP\JOB.OUT
echo Dest Dir : '%2' >>D:\MYTEMP\JOB.OUT
echo Process # : '%3' >>D:\MYTEMP\JOB.OUT
So if your job starts the batch file properly, then after it executes, you should find the file D:\MYTEMP\JOB.OUT containing the argument values you passed in. So is your difficulty on the DOS/Win batch file side or in starting the job?
...roboticus
When your only tool is a hammer, all problems look like your thumb. | [reply] [Watch: Dir/Any] [d/l] |
That is exactly what I'm trying to do. The problem is that I have not hit upon the correct format for passing the arg value for the process number. Instead of the actual value I wind up passing what ever I had there, like $pnumber$.
| [reply] [Watch: Dir/Any] |