Stop Cyclic Run

When specified, this parameter prevents subsequent iterations of the current cyclic job. Cyclic jobs normally run on regular intervals for as long as specified scheduling criteria are satisfied.

If the related On Statement/Code criteria is satisfied, Stop Cyclic Run prevents future iterations of the current cyclic job. If the current job is not a cyclic job, this parameter has no effect on job processing. If a cyclic job is terminated by a Stop Cyclic Run parameter, the View Details screen displayed by option Z in the ctmpsm utility contains Cyclic:T where T indicates "Terminated".

NOTE: To provide logic to stop a cyclic job (for example, if the job ends not OK), create the relevant On statement followed by a Do Stop-cyclic statement in the Do Actions window. You can use the Keep Active for parameter for cyclic jobs as well as non-cyclic jobs, to determine the maximum number of days the job can remain in the Active Jobs database after its order date has passed, if the job has not yet been submitted.

EXAMPLE: A job that updates flight times for an airline should cycle through every 3 minutes from the end of the previous run. If for some reason it fails, it should trigger an alternative flight update program, send a message to the administrator, and stop running. Do the following:

1. In the Scheduling tab select the Cyclic checkbox and click Set.

The Cyclic Job Run Times window appears.

2. Select Rerun Every checkbox and then select 3 minutes.

3. In the All Intervals are from Job's field, select End.

4. Click OK.

5. In the Maximum Reruns field, select 99 as the maximum reruns value.

6. In the Actions tab, add an On-Do Action by doing the following:

• In the On field, select Job ended Not OK.
• In the Do field, select Stop Cyclic run.
• Add another On Do Action by clicking Add Do and in the Do field, select Notify.
• In the Destination file select Alerts Window, type the message Flight updates cannot be sent and select Very Urgent in the Urgency field.