Recovering from errors on the current-plan-extension data set
IBM Tivoli Workload Scheduler for z/OS maintains the current-plan-extension file in a data space. The data space is loaded from the EQQCXDS file on DASD. When a current plan backup occurs, the data space is refreshed to the EQQCXDS data set. If an error occurs on the data set, IBM Tivoli Workload Scheduler for z/OS attempts initial recovery by copying the data space to the data set. If this is not possible, the file must be re-created.
If the EQQNCPDS and EQQNCXDS data sets are valid, perform these actions:
- Cancel IBM Tivoli Workload Scheduler for z/OS.
- Allocate a new CX data set.
- If you allocated the data set with a new name, update all JCL (ddname EQQCXDS) to reference the new data set.
- Specify CURRPLAN(NEW) on the JTOPTS statement.
- Start IBM Tivoli Workload Scheduler for z/OS.
- Remove CURRPLAN(NEW) from the JTOPTS statement.
If you are scheduling end-to-end with fault tolerance capabilities, perform the following manual actions to make sure that the Symphony™ file is aligned with the rebuilt current plan:
- From OPC dialog select the option 3, DAILY PLANNING. The Producing OPC Daily Plans dialog is displayed.
- Then, select option 5, SYMPHONY RENEW.
- Submit the symphony renew batch job to create a Symphony file aligned with the Current® Plan.
If the EQQNCXDS data set is valid but no valid EQQNCPDS data set exists, perform these actions:
- Cancel IBM Tivoli Workload Scheduler for z/OS.
- Allocate a new CX data set.
- If you allocated the data set with a new name, update all JCL (ddname EQQCXDS) to reference the new data set.
- Copy EQQNCXDS to EQQCXDS.
- Specify CURRPLAN(CURRENT) on the JTOPTS statement. CURRENT is the default value.
- Start IBM Tivoli Workload Scheduler for z/OS.
If both EQQNCPDS and EQQNCXDS cannot be used, you must create a new current plan from the LTP. Re-creating the current plan from the long-term plan describes how you do this.