|
|
|
|
|
Specifies a range of steps in the steps of an On program step statement.
This parameter is only relevant for z/OS.
Additional information |
Description |
|---|---|
Usage |
Optional |
Format |
Consists of the Name, From, and To sub-parameters described below. |
Invalid Characters |
None English characters. |
Variable Support |
None |
Alternate names |
|
Sub-parameters |
|
Name
|
Name for the range. 1through 7 characters. Only trailing blanks are allowed in this field. |
From |
First program step or program step, procedure step in the range. Program step is the step name in the EXEC statement that identifies the program to be executed: //pgmstep EXEC PGM= pgmname Procedure step is the step name in the EXEC statement that invokes the procedure: // procstep EXEC procname Program step values and procedure step values can each be from 1 through 8 characters in length, and must not contain blanks. Non-English characters not allowed. |
To |
Last program step or program step, procedure step in the range. The To sub-parameter is optional. If blank, its value defaults to the last step in the job. Non-English characters not allowed. |
Whenever a Step Range statement is specified, it eliminates the need to define separate On program step, On procedure step and On Codes statements and accompanying Do actions for each step in the range. The defined Step Range Name can be used (without redefining the range) in subsequent On program step, On procedure step, and On Codes statements, by specifying the Step Range Name, preceded by an asterisk (*), in the On program step field.
Any number of step ranges can be specified. After entering a Step Range parameter, another Step Range parameter line is automatically displayed.
Using all runs of a job including restarts
When processing On blocks, Control-M can incorporate the results of all previous runs and restarts, filtering them for jobs restarted with the Control-M for z/OS RESTART, RECAPTURE CONDITION or ABEND CODES parameters. Control-M/Restart searches previous runs to determine which steps must be considered part of the restarted job.
For example, if one step finished successfully during its original run and another step finished successfully after a restart, the On block check for the successful finish for both steps produces a TRUE result and the On statement is satisfied.
Activation of this facility requires that the Control-M for z/OS ALLRUNS parameter in the CTRPARM member be set to YES. When activated, this facility may apply to any specified step, step range, or to the +EVERY step value.
Parent Topic |