|
|
|
|
|
Sometimes the decision whether to execute a particular step is dependent upon the execution results (resulting condition code or abend code) of a previous step. The COND JCL parameter and IF/THEN/ELSE JCL statements are commonly used to establish this dependency.
For example, if the following statement is specified
//STEPF EXEC ...,COND=(04,EQ,STEPB)
STEPF is executed only if STEPB did not terminate with a condition code of 04.
If the backward-referenced step is not executed in the restart run because it was executed in the previous run, the condition code or abend code information from the backward-referenced step would not normally be available for the COND or IF/THEN/ELSE JCL statements.
The Condition Code / Abend Code Recapture facility analyzes the SYSDATA of the previous runs of a job order. It determines the condition codes and abend codes of backward-referenced steps and makes the recaptured values available during the restarted run.
The Condition Code / Abend Code Recapture facility allows resetting those values to "ended OK" and/or "not abended" states with zero condition codes for previous "not OK" condition codes and abended steps.
These codes can then be used by the COND parameter and IF/THEN/ELSE JCL statements.
If the ALLRUNS parameter in the CTRPARM member in the IOA PARM library is set to YES, the recaptured codes are also available for Control-M to use when evaluating the previous runs or restarts of a job during post processing. For example, if one step finished successfully in an original run and another step finished successfully after a restart, an ON block containing both criteria are satisfied by the successful step in each of the runs.
By default, condition code recapture and abend code recapture operate automatically. They can also be set using the following methods:
On the other hand, you can reset or suppress these facilities in the following ways:
Parent Topic |