Re-creating the current plan from the new-current-plan and the JT archive log

If all current plan data sets have been damaged or lost but the new current plan still exists and is valid, it is possible to get IBM Tivoli Workload Scheduler for z/OS to take over the new current plan again. This is a better alternative than using refresh because the resulting current plan will normally be up-to-date.

Perform the following procedure:

1. Stop IBM Tivoli Workload Scheduler for z/OS.
2. Add keyword CURRPLAN(NEW) to the JTOPTS statement. When you start IBM Tivoli Workload Scheduler for z/OS, it will:
   1. Use the new current plan data sets (EQQNCPDS and EQQNCXDS) as input
   2. Copy EQQNCPDS to either EQQCP1DS or EQQCP2DS
   3. Copy EQQNCXDS to EQQCXDS and then load the CX data space from EQQCXDS.
   4. Apply all events from the job-tracking archive log (EQQJTARC). If IBM Tivoli Workload Scheduler for z/OS did not end normally, events are applied also from the job-tracking log that was in use when IBM Tivoli Workload Scheduler for z/OS ended.
   In this way, IBM Tivoli Workload Scheduler for z/OS re-creates the current plan.
3. Start IBM Tivoli Workload Scheduler for z/OS.
4. 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:

1. From OPC dialog select the option 3, DAILY PLANNING. The Producing OPC Daily Plans dialog is displayed.
2. Then, select option 5, SYMPHONY RENEW.
3. Submit the symphony renew batch job to create a Symphony file aligned with the Current® Plan.