Contents of the disaster recovery PDS

Edit online

When the disaster recovery job that was created is built and submitted, the following members are generated in the specified disaster recovery PDS.

Table 1. Members generated in the disaster recovery PDS
Member name Contents
ssid#DRC

If the DR profile indicated that the DR preparation job should be saved in the DR PDS, then this job contains a copy of the DR preparation job that was used to create the members of the DR PDS. If your DR environment is set up to use the archive logs, image copies, and change accumulation data sets with the same names as those in the RECON data sets, then you can ship a new copy of the RECONs to the DR site and re-execute this job to create a new DR PDS to a new recovery point.
ssidSKP1,2 Control cards for the Disable old backup in DR PDS function of the DR profile.
ssid#Snn

A series of jobs is created depending on the options specified in the DR profile. Each job performs a specific function, but the member names might change depending on the options. Each member is documented internally to indicate what the job does. The processes that these jobs perform include:

  • Restore the IMS Recovery Expert repository data sets.
  • If coordinated IMS and Db2® recovery was requested, locate a common recovery point between IMS and Db2 and modify the IMS jobs to include the recover to timestamp.
  • Perform system restore from a system level backup (if requested).
  • Delete, define, and recatalog data sets needed for application recovery.
  • Restore the conditioned RECON data sets.
  • Perform application recovery (when system recovery profiles are not being used). If the Recover IMS catalog first option is enabled, two JCLs are created: one is for IMS catalog DBDS recovery and the other one is for other DBDS recovery.
  • Perform pre-recovery when system recovery profiles are being used.
ssid#nnn

If system recovery profiles are used for disaster recovery processing, one or more of these jobs will be created where nnn is a number from 000 through 998.

One ssid#nnn job is created for each user defined system recovery profile. These jobs perform application recovery for the databases defined within the specified system recovery profile.

Run these jobs after the pre-recovery job completes successfully. These jobs do not exist if system recovery profiles are not used.

If the Recover IMS catalog first option is enabled and the IMS catalog DBDSs are defined in the system recovery profile, two jobs are created for the profile: one is for IMS catalog DBDS recovery and the other one is for other DBDS recovery. By running the ssid#nnn jobs in ascending order of the job member name, IMS catalog DBDSs are recovered prior to other DBDSs. The pre-recovery job JCL shows which profiles are associated with IMS catalog DBDSs as shown in Figure 1.
Figure 1. Pre-recovery job JCL example
//*  CAUTION: Members with CATALOG_RECOV=ONLY specified in the list    *
//*  must be completed before other jobs are started. If multiple      *
//*  CATALOG_RECOV=ONLY jobs exist, each job must be completed         *
//*  in ascending order of the member name.                            *
//*                                                                    *
//*   CATALOG_RECOV                                                    *
//*    ONLY: Recover only the IMS catalog DBDSs defined in the profile.*
//*    EXCL: Recover the DBDSs defined in the profile except for IMS   *
//*          catalog DBDS.                                             *
//*    N/A:  No IMS catalog DBDS is defined in the profile             *
//*                                                                    *
//*  Member    Profile Name                    CATALOG_RECOV           *
//*  --------  ------------------------------  -------------           *
//*  IFA#000   PROF-B                          ONLY                    *
//*  IFA#001   PROF-A                          ONLY                    *
//*  IFA#002   PROF-A                          EXCL                    *
//*  IFA#003   PROF-B                          EXCL                    *
//*  IFA#004   PROF-C                          N/A                     *
//*  IFA#999   DEFAULT SYSTEM RECOVERY         N/A                     *
In order to make recovery process simple, it is recommended that you define a system recovery profile covering all IMS catalog DBDSs. Then, the ssid#000 job will be the only job for IMS catalog DBDS recovery as shown in Figure 2.
Figure 2. Pre-recovery job JCL example
//*  CAUTION: Members with CATALOG_RECOV=ONLY specified in the list    *
//*  must be completed before other jobs are started. If multiple      *
//*  CATALOG_RECOV=ONLY jobs exist, each job must be completed         *
//*  in ascending order of the member name.                            *
//*                                                                    *
//*   CATALOG_RECOV                                                    *
//*    ONLY: Recover only the IMS catalog DBDSs defined in the profile.*
//*    EXCL: Recover the DBDSs defined in the profile except for IMS   *
//*          catalog DBDS.                                             *
//*    N/A:  No IMS catalog DBDS is defined in the profile             *
//*                                                                    *
//*  Member    Profile Name                    CATALOG_RECOV           *
//*  --------  ------------------------------  -------------           *
//*  IFA#000   PROF-A                          ONLY                    *
//*  IFA#001   PROF-A                          EXCL                    *
//*  IFA#002   PROF-B                          N/A                     *
//*  IFA#003   PROF-C                          N/A                     *
//*  IFA#999   DEFAULT SYSTEM RECOVERY         N/A                     *
ssid#999

If system recovery profiles are used for disaster recovery processing, this job is created to perform application recovery against any databases that require additional recovery and that were not recovered by one of the ssid#nnn jobs. This job executes application recovery against the default system recovery profile.

Run this job after the ssid#nnn job has completed successfully. This job does not exist if system recovery profiles are not used.

ssidALLC IDCAMS control cards to allocate the IMS WADS, OLDS, RECONs.
ssidCPYL Control cards for copying the archive logs from the tape to the recovery site.
ssidDBDL IDCAMS control cards to delete all database data sets.
ssidDBDF IDCAMS control cards to define all database data sets.
ssidDBRC JCL to delete any subsystem records and close any open logs.
ssidCATL IDCAMS control cards to catalog image copy data sets.
ssidDELC IDCAMS control cards to delete the IMS WADS, OLDS, RECONs.
ssidGDG1,2,3 IDCAMS control cards to allocate GDG bases for archive logs, image copy data sets, and change accumulation data sets.
ssidRCAT IDCAMS control cards to re-catalog archive log data sets on disk.
ssidRECN A copy of the conditioned RECON data set in 80 byte records.
ssidTIME Information needed for performing IMS recovery; and if coordinated IMS and Db2 recovery is being performed, it also contains information for Db2 recovery. This includes timestamps of System Level Backups and archives.
BSYREPOC IDCAMS control cards to allocate the IMS Recovery Expert repository data sets.
BSYREPOD A copy of the IMS Recovery Expert repository in 80 byte records.