How to check if conditional successors are prevented from running

In the CSU£ column you see the number of conditional successors for the job displayed in the JOBNAME column. If this number is 0, then that job has no conditional successors. If the number is greater than 0, then the job has conditional successors and their status depends on how the rule is set in the condition.

The Unexpected RC field XRC indicates if something unexpected occurred and leaves some conditions in Undefined status preventing conditional successors from running.

The job processing is blocked if CSU£ is greater than 0 and the value listed under the XRC column is set to Y.

You can filter by XRC (Unexpected RC) both on ERROR LIST (ISPF 5.4 or 6.4) and OPERATION LIST (ISPF 5.3 or 6.3) panels. For each operation listed, you can check conditional successors and their conditions by using the row command I from error list or B from operation list. The OPERATION DETAILS panel EQQSOPSP is displayed and gives you additional information about what was incorrect or unexpected in the path.

To investigate in more detail you can also look for warning messages EQQE141W and EQQE142W issued in EQQMLOG and in the console log.
Note: When messages EQQE127W and EQQE141W are issued a manual intervention is required to allow job processing to proceed.

If you find, the message EQQE142W in the log, it means that, when the step-end event, identified in the message text by STEPNAME PROCSTEP, was received, the scheduler evaluated that existing conditional and normal successors would never have run due to conditions definitions. For example, see the example in Examples of step-level conditional dependencies evaluation.

If you find the message EQQE141W in the log, one of the following events occurred:
  • When the status of the job indicated in the message became ST, the scheduler evaluated that existing conditional and normal successors would never have run due to conditions definitions. For example, see the example in Examples of job conditional dependencies evaluation.
  • You defined a step dependency for a step that does not exist in the referenced job. The scheduler recognizes that there is a missing step and issues the warning message EQQE127W, when the job ends, it evaluates that successors will never run and issues the warning message EQQE141W, even if the origin of the problem is in the step definition. For example, see the example in Examples of step-level conditional dependencies evaluation.