Shadow job status transition during the remote job recovery or rerun

If the shadow job is used to map locally the status transition of a remote job with recovery job, prompt or options defined, the following behavior occurs:

• The shadow job status remains STARTED with extended status RECOVERY_IN_PROGRESS while the remote job recovery is in progress.
• The shadow job status is updated only when the remote job reaches a final state. The shadow job status will become:

  ERROR

  When the remote job final status notified is FAILED_EXECUTION or FAILED_SUBMISSION..

  COMPLETE

  When the remote job final status notified is SUCCEDED_EXECUTION.

It might happen that the remote job is rerun, either manually or as result of an automatic recovery. If the remote job was already completed successfully then the rerun has no impact on the shadow job status because it was already SUCC. If the remote job rerun requires the change of the shadow job status from ERROR to STARTED, HCL Workload Automation for Z applies the change if:

• The shadow job has no conditional successors.
• The shadow job is a conditional predecessor and its status change does not cause inconsistencies in the condition evaluation.

If the shadow job status change from ERROR to STARTED causes inconsistencies in evaluating conditions where the shadow job is a conditional predecessor, HCL Workload Automation for Z automatically sets the status of the shadow job to ERROR with error code OSEQ.

You can see the information about the remote job status:

• In the extended status of the shadow job displayed on the SELECTING APPLICATION OCCURRENCE AN OPERATION INFORMATION panel.
• In the Extra Information fields in the shadow job properties panel on the Dynamic Workload Console.