FLUSH

The CODES value FLUSH generally applies when a step does not run but no error is indicated. This CODES value is assigned in the following cases:

• A JCL COND or JCL IF/THEN/ELSE statement caused the step not to run. Control-M detects CODES value FLUSH steps by message IEF272I (Step was not executed).
• §Restart§ If a job was restarted by Control-M/Restart, and Control-M is to consider all job runs during post-processing (the ALLRUNS parameter is set to YES in the CTRPARM member), a step is defined as FLUSH if:
  • either the step did not previously run, or Control-M/Restart did not recapture a completion or abend code from a previous run

    and either

  • it was not executed during the RESTART run because of a JCL COND or JCL IF/THEN/ELSE statement

    or

  • it was not executed due to a RESTART decision (message CTR103I)

Because a CODES value of FLUSH does not indicate that an error occurred during job execution, assignment of this status does not cause a job status of NOTOK.

If a JCL statement other than the COND or IF/THEN/ELSE statement caused the step not to run, it is not defined as a FLUSH step.

If the failure of a step causes subsequent steps not to be executed, these subsequent steps are not defined as FLUSH steps.

For reasons of backward compatibility, that is, to ensure that the application of CODES value ***** remains unchanged, CODES value ***** does not include FLUSH steps.