Recovery to start-of-day processing

A disaster recovery plan that recovers to start-of-day processing is, perhaps, the easiest backup process to implement. The following text describes the backup schedule required to support the recovery process to start-of-day processing.

Backup requirements

Table 39 defines the backup intervals required to ensure that you can successfully restore IBM Tivoli Workload Scheduler for z/OS to start-of-day processing. N/A shows that a backup is not applicable for DRP purposes.

Table 39. Backup cycle for start-of-day DRP
ddname Format Defines Backup interval
EQQADDS VSAM Applications and JCL variables Daily
EQQCKPT PS Checkpoint data set N/A
EQQCP1DS VSAM Current-plan-1 data set N/A
EQQCP2DS VSAM Current-plan-2 data set N/A
EQQCXDS VSAM Current-plan-extension data set N/A
EQQDLnn PS Dual job-tracking-log data set N/A
EQQEVDS PS Event data set for the event-writer task N/A
EQQEVDnn PS Event data set for an event-reader task N/A
EQQHTTP0 PS Event data set for end-to-end scheduling with z-centric capabilities N/A
EQQINCWK PS JCC incident work file N/A
EQQJBLIB PDS JCL library data set Minimum weekly, daily if high activity
EQQJCLIB PDS JCC message-table data set Minimum weekly, N/A if same as primary
EQQJS1DS VSAM JCL-repository-1 data set N/A
EQQJS2DS VSAM JCL-repository-2 data set N/A
EQQJTARC PS Job-tracking-archive data set N/A
EQQJTnn PS Job-tracking-log data set N/A
EQQLDDS VSAM Work data set for long-term-plan batch jobs N/A
EQQLTBKP VSAM Long-term plan backup See note 1
EQQLTDS VSAM Long-term plan data set See note 1
EQQMLIB PDS Message library N/A (already in secondary)
EQQMLOG PS Message log N/A
EQQNCPDS VSAM New-current-plan data set N/A
EQQNCXDS VSAM New-current-plan extension data set N/A
EQQOIDS VSAM Operator-instruction database Minimum weekly, daily if high activity
EQQPARM PDS

Initialization-statement-parameter library

Initialization-statement- parameter library

 Minimum weekly, daily if high activity
EQQPRLIB PDS Automatic-recovery-procedure library Minimum weekly, daily if high activity
EQQRDDS VSAM Special resource descriptions Daily
EQQSCLIB PDS Scripts and Command library Minimum weekly, daily if high activity
EQQSIDS VSAM ETT criteria and configuration data Minimum weekly, daily if high activity
EQQSTC PDS Started-task-submit data set N/A
EQQSUDS PS Submit/release data set N/A
EQQTWSCS PDSE End-to-end data set for centralized script support N/A
EQQTWSIN PS Input events for end-to-end scheduling with fault-tolerance capabilities N/A
EQQTWSOU PS Output events for end-to-end scheduling with fault-tolerance capabilities N/A
EQQWSDS VSAM Workstation, calendar, and period definitions Minimum weekly, daily if high activity
EQQYPARM PDS Initialization statements parameter library Minimum weekly, daily if high activity
STEPLIB PDS Tivoli Workload Scheduler for z/OS load-module library N/A (already in secondary)
user-defined PS Submit/release data set N/A
Notes:
  1. When an LTP or daily-planning batch job runs a copy of the LTP is written to the EQQLTBKP data set. Use EQQLTBKP for your DRP backup to ensure that no updates have occurred before the backup is taken. Perform the DRP backup daily.
  2. Tivoli Workload Scheduler for z/OS issues message EQQN057I to show that a CP backup is complete. You should update the message to include WTO=YES so you can use NetView® to trigger DRP data set backups. Message EQQN051I shows why the CP backup occurred. The DRP backups can be triggered when the scheduler issues message EQQN057I following message EQQN051I with reason "DP END". In fact, now, EQQLTBKP, EQQNCPDS and EQQNCXDS are all synchronized with the other scheduler data.

Recovery process

Follow the steps listed below to recover your Tivoli Workload Scheduler for z/OS environment to start-of-day processing.

  1. Allocate all required data sets. The JCL required should be based on the sample library (SEQQSAMP) members EQQPCS01 and EQQPCS02.
  2. Restore data from the last backup taken before the start-of-day required. For example, if recovery to start-of-day for Tuesday is required, then backups from Monday should be used for the recovery.
  3. Specify JOBSUBMIT (NO) and CURRPLAN (NEW) on the JTOPTS statement and then start the controller address space. Start additional address spaces required for tracker subsystems.
  4. If required, use the mass update function in the Application Description dialog to make out-of-effect business systems that you do not need to process in the secondary center.
  5. Submit a long-term plan MODIFY ALL batch job.
  6. Submit a daily plan TRIAL for the required planning period, and check the results. It is recommended that you start the planning period from 00:00 on the date required to reduce the number of undecided occurrences included in the current plan.
  7. Submit a daily plan EXTEND batch job for the required planning period. Use 00:00 as the start time. When the new current plan is created, use the Tivoli Workload Scheduler for z/OS dialogs to check that occurrences and resources are in the correct status before starting job submission.
  8. Change CURRPLAN(NEW) to CURRPLAN(CURRENT) on the JTOPTS statement.