Control-M/Restart users can use the Set Restart Options parameter to restart the failed job instead of using the Rerun Member parameter to rerun the job.
The automatic rerun process works as follows:
Control-M determines that automatic rerun is possible only if the job ends NOTOK and a specified Rerun Job statement is activated during post-processing. If Control‑M determines that automatic rerun is possible, it sets the job’s status to ended NOTOK – RERUN NEEDED.
Control‑M then checks the value of Maximum reruns in the Active Jobs database. If the value is zero (or no maximum reruns value was specified), automatic rerun is not possible and the job is not submitted for rerun. If the value is greater than zero, rerun is possible and the monitor submits the job for rerun when all runtime criteria are satisfied. Runtime criteria include not only the Runtime Scheduling parameters, but also the Rerun using the following interval sequence parameter, which specifies the minimum allowable interval between runs of the same job.
The JCL for the rerun job is taken from the member specified in the Rerun Member parameter. If no Rerun Member value is specified, the JCL for the rerun is taken from the job’s regular JCL member specified in the File name/Member name parameter.
Rerun Member has additional characteristics:
The member name can be the same as, or different from, the job name.
The member specified in the Rerun Member parameter must be in the library specified in the File Path/Member library parameter.
The Rerun Member parameter overrides the Member name parameter value in the JCL, and the Member name parameter value becomes irrelevant for reruns.
Availability
This parameter is relevant only for z/OS jobs.
The Set Restart Options and Rerun Member parameters cannot be specified together.
The Rerun Member parameter cannot be specified for cyclic jobs and cyclic started tasks.