Current-plan processing at Tivoli Workload Scheduler for z/OS startup
This section describes the two current plan processing conditions that can occur when:
- Starting IBM Tivoli Workload Scheduler for z/OS with an empty checkpoint data set
- Starting IBM Tivoli Workload Scheduler for z/OS with a valid checkpoint data set.
Starting Tivoli Workload Scheduler for z/OS with an empty checkpoint data set
The checkpoint data set is empty the first time IBM Tivoli Workload Scheduler for z/OS is started. It is also empty if it has been deleted and reallocated for some reason, such as if it was damaged.
When IBM Tivoli Workload Scheduler for z/OS is started for the first time, the following occurs:
- The checkpoint data set is formatted and initial values written to it.
- When JTOPTS CURRPLAN(CURRENT) is specified, IBM Tivoli Workload Scheduler for z/OS will issue message
EQQN026W A NEW CURRENT PLAN (NCP) HAS BEEN REJECTEDand stop processing.
- When JTOPTS CURRPLAN(NEW) is specified, IBM Tivoli Workload Scheduler for z/OS carries out recovery
processing using the new current plan (EQQNCPDS and EQQNCXDS) as described
in Current-plan
recovery processing. There might be a new current plan if you
are migrating from a previous release or version and you have placed
the converted current plan in the new current plan data sets as part
of the migration procedure.
If the new current plan is empty, recovery processing ends, IBM Tivoli Workload Scheduler for z/OS becomes active without a current plan, and job tracking is not started.
- If recovery processing with the new current plan is successful, IBM Tivoli Workload Scheduler for z/OS starts normal processing.
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 you start IBM Tivoli Workload Scheduler for z/OS after having deleted and reallocated the checkpoint data set, and you specified JTOPTS CURRPLAN(NEW), the following occurs:
- IBM Tivoli Workload Scheduler for z/OS carries out recovery processing with the new current plan as described in Current-plan recovery processing.
- IBM Tivoli Workload Scheduler for z/OS normal processing starts.
Starting Tivoli Workload Scheduler for z/OS with a valid checkpoint data set
A valid checkpoint data set should exist even if IBM Tivoli Workload Scheduler for z/OS ended unsuccessfully the previous time.
When IBM Tivoli Workload Scheduler for z/OS starts, it reads the checkpoint data set to determine which is the active current plan and job-tracking log.
The job-tracking log is opened. If no job-tracking records are found, this indicates that IBM Tivoli Workload Scheduler for z/OS ended normally because a JT log switch is performed when the CP backup completes at normal termination.
If there are records on the job-tracking log after the backup position, this indicates that IBM Tivoli Workload Scheduler for z/OS did not end normally. In this case, recovery processing using the backup current plan and CX data set is performed as described in Current-plan recovery processing. Normal IBM Tivoli Workload Scheduler for z/OS processing is then started.
If the Symphony file is not up to date with the Current Plan, select the option 5 on the panel Producing OPC Daily Plans or submit the Daily Plan batch job.