Maximum reruns

Determines the maximum number of reruns that can be performed for the job.

Additional information	Description

Usage	Optional
Length	An integer from 0 through 99. z/OS: There is a difference between cyclic jobs and regular jobs: Cyclic jobs – an integer from 0 through 9999 Regular jobs – an integer from 0 through 255.
Default	0
Variable Name	None
Alternate names	Control‑M/EM Utilities: MAXRERUN Control-M Report: MAX RERUN Control‑M/Server Utilities: -maxrerun Control‑M for z/OS: MAXRERUN Control‑M/EM API: rerun_max
Computer specific information
z/OS	When a job is first run, the Maximum reruns field in the Active Jobs database, that is, in the Zoom screen, contains the same value as the Maximum reruns parameter in the job scheduling definition. However, in the Active Jobs Database Maximum reruns works as a "reverse-counter" of automatic reruns. Each time the job is automatically rerun, the value is decreased by one until the field contains a value of zero.

EXAMPLE: When MAXRERUN is set to 1 the RUNCOUNT will have a value of 2 before the job stops executing.

When the job’s completion status is set to Rerun using the Rerun Job parameter, Control‑M checks the number of reruns specified in the Maximum reruns parameter. If the number in the Maximum reruns parameter is greater than the number of reruns that have already been performed for the job, a rerun (automatic rerun) process is performed for the job.

When a job is assigned Rerun status, the job is not rerun if either

Maximum = 0
The number of reruns specified in this parameter has already been performed

Control‑M waits at least the number of minutes specified by the Interval parameter before it attempts the next rerun of the job.

The job is re-submitted after

The specified number of minutes has elapsed from the last rerun

-and-

all submission criteria are satisfied

A rerun counter is displayed on the Monitoring domain of the job properties pane, indicating how many times the job has been rerun from the current job order.

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 the monitor determines that automatic rerun is possible, it sets the status of the job to ENDED NOTOK – RERUN NEEDED.
The monitor then checks the value of Maximum reruns in the Active Jobs database. If the value is zero, 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.
The JCL for the rerun job is taken from the member specified in the RERUNMEM parameter. If no RERUNMEM value is specified, the JCL for the rerun is taken from the regular JCL member of the job that is specified in the MEMNAME parameter.

Maximum reruns applies only to automatic reruns. The Maximum reruns counter is not affected by reruns performed manually using the Rerun option in the Control‑M for z/OS Active Jobs database screen.

If a job is defined as cyclic or it is defined as a Cyclic SMART Folder, the Maximum reruns parameter can be used to specify the number of iterations. This number excludes the initial run of the job/Cyclic SMART Folder.

Parent Topic

Scheduling Parameters