Recovering your system at the remote site

Edit online

Follow these steps at the remote site to recover your system.

Procedure

  1. Restore the recovery PDS that was created by the disaster recovery preparation job at the local site.

    The following figure is an example of the JCL used to restore this file:

    Figure 1. Example: JCL to Restore Recovery PDS
    //RESTORE   JOB ...                                                       
//COPY      EXEC PGM=IEBCOPY                                       
//SYSPRINT  DD   SYSOUT=A                                              
//SYSUT1    DD   DSNAME=disaster.recovery.pds.backup,     
//                    UNIT=tape,LABEL=(,SL),                    
//                    VOL=SER=xxxxxx,DISP=OLD                   
//SYSUT2    DD   DSNAME=disaster.recovery.pds,                 
//                    UNIT=disk,VOL=SER=xxxxxx,                
//                    DISP=(NEW,KEEP),SPACE=(CYL,(10,5,10))    
//SYSUT3    DD   DSN=TEMP1,UNIT=disk,VOL=SER=xxxxxx,           
//                    DISP=(NEW,DELETE),SPACE=(80,(15,1))      
//SYSIN     DD   DUMMY                                         
/*

  2. Run the ssid#S01 job. This job deletes, redefines, and then reloads the repository data sets. If you are recovering multiple SSIDs that use the same repository data sets, you should only run this job once for all SSIDs. If you run this job multiple times, then active data from the DR site might be destroyed or duplicate records might be added.
  3. Review and execute the ssid#S02 through ssid#Snn jobs to perform the steps required to restore the IMS system data sets (if requested) and IMS database data sets, and perform application recovery (if requested).

    These jobs will perform the following processes, as requested:

    • If recovery is being performed using a System Level Backup, the ssid#S02 job will restore the IMS system from the SLB. After this job is run, ensure that all user catalogs are connected and all aliases are defined for the IMS subsystem.
    • Delete and redefine the OLDS, WADS, and RECON data sets.
    • If the image copy DR method is being used, then delete and redefine all database data sets.
    • Delete and redefine any GDG bases needed for archive logs, image copies, or change accumulation data sets.
    • Recatalog any archive logs that are on tape.
    • Rebuild the RECON data sets from the ssidRECN member of the DR PDS.
    • Copy archive logs to DASD.
  4. If System Recovery Profiles are not being used, the last ssid#Snn job will perform application recovery for all database data sets according to the recovery options that you specified in the DR profile. If System Recovery Profiles are being used, this job will perform application pre-recovery (such as running Change Accumulation if requested). After this job completes, run the ssid#nnn jobs as follows:
    1. Run the ssid#nnn jobs. If system recovery profiles are used, run the ssid#nnn jobs (where nnn is a number from 000 through 998) to perform application recovery. These jobs execute the user defined system recovery profiles to perform recovery on the databases specified in the profile. These jobs will not exist if system recovery profiles are not being used.
      If the Recover IMS catalog first option is enabled, you must complete the application recovery jobs for IMS catalog database prior to other databases. See also ssid#nnn in Contents of the disaster recovery PDS.
    2. Run the ssid#999 job. If system recovery profiles are used, run the ssid#999 job to perform application recovery against the default system recovery profile. This job will perform database recovery for all databases that require recovery and that were not included in the ssid#nnn jobs. This job will not exist if system recovery profiles are not being used.
  5. When you have completed these steps, restart IMS.