
This Month's Tool Tip
How to halt initiates after a Suppressed Run job
SUMMARY
This article describes how keep jobs from being initiated after a job run that is suppressed using resource statements
MORE INFORMATION
EnterpriseSCHEDULE allows the suppression of job runs based on the outcome of resources. For instance if you want to suppress job runs after 10:00 PM you can add the following resource statement to a job”
If $Time .gt. 1000 then suppress_run
In this case, if the job was run after 10:00 PM, the job would run, it’s commands would be suppressed and it would run any initiates that followed.
In some cases, a user may want to halt initiates after a job is suppressed. This is addressed in this FAQ.
STOPPING INITIATES AFTER A SUPPRESSED RUN
Since jobs that are suppressed exit with a specific status code, we can put a condition on all initiates after the potential suppressed runs to keep the initiate from taking place. This condition essentially says that if the initiating job does not exit with a suppressed run status, initiate the next job.
In order to make an initiate conditional on the suppressed_run status of the job,
- Select the initiate from the Connections tab on the initiating job's property page.
- Click the Edit button.
- When the initiate dialog comes up, click More.
- Add the following condition.

This will prevent job25 from being initiated if job14 is suppressed.
For the complete FAQ go to: FAQ 326.