Examples of step-level conditional dependencies evaluation

If you configured IBM Z Workload Scheduler to track step-end events, then the step dependencies are checked at step-end time when the return code value is available.

This section contains an example showing how operation processing flow is affected when using step-level conditions.

Figure 1 shows an example of conditional dependency logic at job step level. In the figure, dotted lines represent conditional dependencies and straight lines represent normal dependencies.
Figure 1. Example of step-level dependency

The graphic shows an example of step-level dependency

In this example:
  • JOBB can start if STEP100, belonging to JOBA, ends with RC=4.
  • JOBC is a normal successor of JOBA and therefore starts if JOBA status is C (Completed).
The operation processing proceeds based on possible STEP100 return codes and JOB_A statuses:
STEP100 ends with RC=4; JOBA status is not yet completed
Figure 2 shows the operation processing flow:
Figure 2. Step dependency status evaluation if Step100 ends with return code 4 and JOBA status is not yet completed

The graphic shows the step dependency status evaluation if Step100 ends with return code 4 and JOBA status is not yet completed

A possible path exists because the step dependency is true and therefore a conditional successor exists. The successor conditions can be evaluated.

JOBB can start processing, if free from other dependencies, even if JOBA has not yet ended processing.

STEP100 ends with RC=8; JOBA status is not yet completed
Figure 3 shows the operation processing flow:
Figure 3. Step dependency status evaluation if Step100 ends with return code 8 and JOBA status is not yet completed

The graphic shows the step dependency status evaluation if Step100 ends with return code 8 and JOBA status is not yet completed

Even though STEP100 ended with a return code different from 4, the successor conditions cannot be evaluated yet because JOBA is not completed and so an existing path in the plan does not exist.
  • The step-level condition is set to U (Undefined).
  • JOBB status is set to W (Wait).
The condition is evaluated again as soon as JOBA ends processing.
STEP100 ends with RC=8; JOBA ends successfully
Figure 4 shows the operation processing flow:
Figure 4. Step dependency status evaluation if Step100 ends with return code 8 and JOBA ends successfully

The graphic shows the step dependency status evaluation if Step100 ends with return code 8 and JOBA ends successfully

A possible path exists because JOBA has completed successfully and a normal successor, JOBC, exists. The step-level condition is evaluated again.
  • JOBC can start processing, if free from other dependencies.
  • The step-level condition status is set to F (False).
  • JOBB status is set to X (Suppressed by condition).
STEP100 ends with RC=8; JOBA ends in error
Figure 5 shows the operation processing flow:
Figure 5. Step dependency status evaluation if Step100 ends with return code 8 and JOBA ends in error

The graphic shows the step dependency status evaluation if Step100 ends with return code 8 and JOBA ends in error

In this case a possible path in the plan does not exist.
  • JOBA ended in error, therefore its normal successor, JOBC is set to W (Wait).
  • The step-level condition is not evaluated again and so its status remains U (Undefined) and JOBB status remains W (Wait).
  • JOBA is marked with the Unexpected RC flag and the warning message EQQE142W is logged in the controller MLOG and in the system log.

Now the operator can examine the reason why JOBA failed and then either rerun the occurrence or fix the error and continue the processing.

No step-end event is received for STEP100; JOBA ends successfully
Figure 6 shows the operation processing flow:
Figure 6. Step dependency status evaluation if no step-end event is received for Step100 and JobA ends successfully

The graphic shows the dependency status evaluation if no step-end event is received for Step100 and JobA ends successfully

A possible path exists because JOBA has completed successfully and a normal successor, JOBC, exists.
  • JOBC can start processing, if free from other dependencies.
  • The step-level condition is left U (Undefined) and the warning message EQQE127W is logged in the controller MLOG and in the system log.
  • JOBB status remains W.
No step-end event is received for STEP100; JOBA ends in error
Figure 7 shows the operation processing flow:
Figure 7. Step dependency status evaluation if no step-end event is received for Step100 and JOBA ends in error

The graphic shows the step dependency status evaluation if no step-end event is received for Step100 and JOBA ends in error

In this case a possible path in the plan does not exist:
  • JOBC status remains W (Wait).
  • The step-level condition is left as U (Undefined) and the warning message EQQE127W is logged in the controller MLOG and in the system log.
  • JOBB status remains W.
  • JOBA is marked with the Unexpected RC flag and the EQQE141W message is logged.