General Information for DO IFRERUN

When a DO IFRERUN statement is specified, the rerun is performed by the Restart facility of Control-M/Restart using the specified restart subparameters.

• When DO IFRERUN is specified with a CONFIRM value of N (No):
  • If a DO RERUN statement follows, the job is automatically submitted for rerun.
  • If a DO RERUN statement does not follow, the job is not automatically rerun. Instead, the job remains displayed with its error status in the Active Environment screen.

    In this case, to submit the job for rerun or restart, specify option R (Rerun) in the Active Environment screen. The Rerun (with Restart) Confirmation Window is displayed. Request the restart or rerun from the window.

• When DO IFRERUN is specified with a CONFIRM value of Y (Yes), the job appears in the Active Environment screen with a WAIT CONFIRMATION (WITH RESTART) status and is not restarted unless confirmed. Specify option C (Confirm) to open the Confirm window to restart the job.

§Restart§ For more information about job restart, see Active Environment Screen.

§Restart§ When a job is submitted for restart, if $FIRST is specified in the FROM subparameter, a $FIRST step specification is passed "as is" to the CONTROLR step. If $ABEND or $EXERR is specified, the specified $ABEND or $EXERR value is first resolved to the appropriate step by the Control-M monitor and then passed to the CONTROLR step. If $FIRST.$ABEND is specified, the Control-M monitor determines which procedure abended and then passes the $FIRST step specification for that procedure to the CONTROLR step. For information regarding the CONTROLR step, refer to the Control-M/Restart User Guide.

§Restart§ The Control-M parameter MAXRERUN determines the maximum number of times the restart or rerun can be performed. For more information, see MAXRERUN: Post–Processing Parameter.