You can define a recovery process to be started as the result of a defined event during job execution. You can also define recovery action at the job level according to Any check not ok. Usually, recovery is used in case of job failure.
The conventional way to trigger a recovery network would be to define an event which activates the recovery network. Recovery is then started only if the event occurs or if any check is not ok.
This document covers the following topics:
| Field | Description | |
|---|---|---|
| Owner | Name of the owner of the recovery network. Default: (same). If you do not change the default, (same) means the owner of the network to be recovered. The default value is replaced at execution time. | |
| Network | Name of network containing the
recovery job(s). Default: (same). If you do not change the default, (same)
means the same network as the one containing the job(s) to be recovered. The
default value is replaced at execution time. When you copy a recovery job to another network, the default values (same) for owner, network, and network version remain unchanged, so that the recovery job can be used unchanged in the network to which it was copied. |
|
| Version |
Network version. Default: (same). If you do not change the default, (same) means the same network version as the one containing the job(s) to be recovered. The default value is replaced at execution time. When you copy a recovery job to another network, the default values (same) for owner, network, and network version remain unchanged, so that the recovery job can be used unchanged in the network to which it was copied. |
|
| Job | Name of the last job in the recovery network. This job must terminate successfully to start rescheduling. | |
| Same Run | Single recovery jobs can be defined in the same network and can be executed under the same run number as the network to be recovered. All active objects of the network are then accessible for the recovery job with this run number. Possible values: | |
| Y | Use same run number (default for single jobs). | |
| N | Use a separate run number for the recovery (default for whole network). | |
| Reschedule | Specifies whether the job is to be rescheduled for submission after recovery. Possible values: | |
| Y | Resubmit the job. | |
| N | Do not resubmit the job. (default) | |
| S | Stop original network after recovery. | |
| Repeat |
Maximum number of times the original job is to be rescheduled after a recovery. Default is 1. The Entire Operations Monitor sets the reserved condition
"Repeat" is meaningful only if "Reschedule" is set to "Y". |
|
| Wait Time | The time to wait in minutes until the recovery is started, and between the recovery attempts. | |
When defining a recovery action, the following Entire Operations system symbols can be prefixed with the escape symbol for symbol prompting and used, for example, in a comment line in the JCL of the recovery job:
| Field Name | Description |
|---|---|
| P-C-OWNER | Owner of the job making the call. |
| P-C-NETWORK | Network of the job making the call. |
| P-C-JOB | Name of job making the call. |
| P-C-RUN | Run number of the job making the call. |
| P-C-SUFFIX | Value of the suffix symbol of the job making the call. |
They are substituted at JCL load with their current values. In the SYSOUT of the recovery job, you can then find the substitution of the parameters:
*** Symbol : P-C-OWNER *** Value : GFR *** Symbol : P-C-NETWORK *** Value : NET-1 *** Symbol : P-C-JOB *** Value : JOB-6 *** Symbol : P-C-RUN *** Value : 208 *** ===================================================== 2 //STEP1 EXEC PGM=NOPCONTI 3 //STEPLIB DD DISP=SHR,DSN=NOP.DEV.LOAD *** CALLING OWNER GFR *** CALLING NETWORK NET-1 *** CALLING JOB JOB-6 *** CALLING RUN 208 ***
In this way you can find out the job making the call, that is, the job to be recovered by the recovery job.