General Information for DO RERUN

The RERUN statement is intended for situations in which a job must be rescheduled following an unsuccessful job run.

Rerun jobs remain in the Active Jobs file with a status of WAIT SCHEDULE, where they wait to be submitted like any other job. However, other parameters, such as CONFIRM and DO IFRERUN, can affect the status of the rerun job order and the submission and processing of the job:

• A Y value specified in the CONFIRM parameter indicates that manual confirmation is required before submitting the rerun job order. In this case, the rerun job order is placed in the Active Jobs file with a status of WAIT CONFIRMATION (FOR SCHEDULE). The job can be confirmed by option C (Confirm) in the Active Environment screen.
• A DO IFRERUN statement before the DO RERUN statement indicates that a restart is desired instead of a full rerun. The job order is placed in the Active Jobs file with a status of WAIT SCHEDULE – WITH RESTART, where the job waits to be submitted from the indicated restart step. Confirmation can also be required for restart jobs. This, too, is performed from the Active Environment screen. For more information, see §Restart§DO IFRERUN: Post–Processing Parameter.

For information about confirmation, see Confirm Rerun Window and §Restart§Rerun and/or Restart Window (Under Control-M/Restart).

Job rerun is also affected by the MAXRERUN, RERUNMEM and INTERVAL parameters.

• MAXRERUN specifies the maximum number of times the job must be scheduled for rerun.
• RERUNMEM specifies the JCL member to be used for the rerun (if different from the normal JCL member of the job).
• INTERVAL specifies the number of minutes to wait between reruns.

These parameters are described in this chapter.

DO RERUN cannot be specified for a cyclic job or a cyclic started task.

DO RERUN cannot be specified for the same ON step and code event as DO OK.

Do not specify DO RERUN for steps that have a specified ON statement code value of OK.

Do not specify DO RERUN for steps that have a specified ON statement code value of NOTOK because many of the causes of a NOTOK status, such as JCL not found, preclude the possibility of a successful job rerun. Instead, specify an ON statement code value of EXERR to accompany the DO RERUN statement.

When a DO RERUN statement is performed for a job (that is, the accompanying ON step and code criteria are satisfied), the previously run job is automatically assigned a final status of ENDED NOTOK, even if the job would have otherwise had a status of ENDED OK.