Job Forcing Considerations
Only one On Spool job can be created in response to a job arrival event. However, in several cases, multiple DO FORCEJOB actions might match the arriving job. Each of these cases and the job forcing logic applied to them, to prevent multiple On Spool processes for the same external job, are described below.
The On Spool process, the match between the external job name and MEMNAME, is performed for the first DO FORCEJOB in the first matching job arrival rule only:
In either case, all subsequent DO FORCEJOB statements in the same rule (if they exist) are handled normally, that is, not as forcing On Spool jobs.
If a table containing more than one job is forced, by the first DO FORCEJOB statement in the rule, as described above, the first matching job causes the job to be an On Spool job. All the other jobs in the table are forced as regular Control-M jobs, even if they match the job name of the external job.
Only the DO FORCEJOB statements from the first triggered rule are executed, as described above. DO FORCEJOB from all other triggered job arrival rules are ignored.
Note: If an On Spool job was purged from the spool but still remains in the Active Jobs file, and another job with the same name arrives on spool and is assigned the same job ID, that later job is not forced.
Parent Topic |