Symptoms
If an Arcana Scheduler or adTempus job runs a batch file that in turn runs other programs, terminating the job in the scheduler only terminates the batch file. Any program(s) that the batch file has already started are not affected.
Cause
The scheduler only has control over the process that it starts, which in this case is the batch file. The scheduler does not have any information about the programs started by the batch file, and therefore cannot terminate them.
More Information
The same circumstance arises if the program run by the scheduler spawns another program to do part of its work.
Workaround
If you need for the scheduler to be able to monitor and control each program in a batch file, you must eliminate the batch file and have the scheduler run each program separately:
- In Arcana Scheduler, create a separate job for each program, and link the jobs together (using options on the Actions page of the job's properties) to run the jobs in sequence.
- In adTempus, create a separate step within the job for each program.
