Creating a system resource recovery job (ARMBSRR)

This procedure creates JCL that you can use in conjunction with copies of the archive logs to restore Db2 system resources at the recovery site.

You can also generate a recovery simulation JCL to verify that you have all resources required for a system resource recovery. (For additional information, see Recovery-simulation.)

Tip

We strongly recommend that you regenerate the JCL for ARMBSRR after you migrate to a newer version of BMC AMI Recovery Manager. This ensures that your JCL is able to take advantage of new features.

Related topics

ARMBSRR-syntax-and-option-descriptions

Preparing-system-resources-for-recovery

Task-5-Preparing-system-resources


Creating a system resource recovery job (ARMBSRR).png

Before you begin

To perform this procedure, you need the following items:

  • Wait for the ARMBARC job (or step) to finish. (See Creating-an-archive-log-copy-job.)

    Important

    For a data sharing subsystem, there are multiple ARMBARC jobs (or multiple job steps).

  • The following authorizations to execute ARMBSRR at the local site:
    • EXECUTE authority on the BMC AMI Recovery Manager DB2 plan
    • READ authority for the archive log data sets and BSDSs
    • APF authority for ARMBSRR
    • READ authority for the ICF catalog
    • READ authority for the archive history file
  • The following information is specific to building the ARMBSRR job:
    • If you will restore the archive logs to disk at the recovery site
    • If you will initialize the recovery site active logs from archive logs
    • if the archive copies will be cataloged at the recovery site (recommended)

  • A GDG base is established for the offsite JCL.

    Important

    Because the ARMBSRR JCL that is created by this procedure is executed regularly, you must create a GDG data set (ARMGDG) to receive the generated JCL that you must then send to the remote site. See the ARMGDG member in the BMC AMI Recovery Manager control library. If you are using SIMULATE YES, set up a GDG base that has a final node ending in SIM or .SIM. (For example, ARMGDG.BASE.SIM or ARMGDG.BASESIM.) This ensures that simulation jobs are not mistaken for recovery jobs. If you are using the Recovery Management for Db2 solution and using ESTIMATE YES, set up a GDG base that has a final node ending in EST or .EST.

  • A model Data Set Control Block (DSCB) name for GDG data sets. SYS1.MODEL can be used if it exists on your system.
  • An archive history file data set (one for each member for data sharing subsystems)
  • A job card that is stored in a data set that has a job name that includes the variables &##

Verify the following configuration option values (in the option set) used by ARMBSRR:

  • The BMC AMI Recovery Manager plan
  • The R+/CHANGE ACCUM plan
  • Whether time stamps are to be used in the names of the archive log copies
  • The version of Db2 that is installed
  • The Db2 subsystem exit and load libraries
  • The PACLOG libraries (optional)
  • Whether the CATALOG parameter is used in IDCAMS specifications
  • Work file database name (for data sharing object sets only)
  • The following Db2 subsystem parameters:
    • VCAT name
    • The BSDS data set names
    • The object set member name (if included in a data-sharing object set)

    • The archive history file data set name

      Important

      In a data-sharing object set, there is one archive history file for each member in the object set.

Db2 should be active to run ARMBSRR; otherwise, some steps in the process are not generated. If ARMBSRR is to be run for a data sharing object set, Db2 must be active on the system where you run the job.

For additional options that are not available from online JCL generation, see ARMBSRR—System resource recovery.

Tip

  • When you use BMC AMI Recovery Manager to make contingency plans for disaster recovery, you should keep the values of the default work unit and space allocations current in the Work File Options Specification panel (available through Subsystem Options on the BMC AMI Recovery for Db2 Main Menu). The ARMBSRR program uses these values to dynamically allocate a significant number of data sets and to calculate catalog and directory space.
  • As a standard practice, you can specify a space that is equal to or larger than the space that is required by your largest directory space.
  • We recommend that you run ARMBSRR only when all target Db2 subsystems are active. However, if a non-data-sharing Db2 subsystem is inactive, some system resource information is obtained from the BMC AMI Recovery Manager option set (see BMC-AMI-Recovery-Manager-option-sets-and-configuration-options).
  • The ARMBSRR program uses the DB2 SYSPLANDEP table to determine the name of the repository to be recovered.

 To create a system resource recovery job (ARMBSRR)

Start this procedure at the BMC AMI Recovery Manager Main Menu.

  1. Access the DB2 Subsystem Toolbox panel, as follows:
    1. Select 3. DB2 Subsystem Toolbox
    2. Select 8. Disaster Recovery Prep
    3. Select 3. Prepare to Recover the DB2 Subsystem

    4. (

      Recovery Management for Db2

       solution only) A separate Mirror Strategy panel appears to enable you to specify your mirroring strategy if you are using the Recovery Management for Db2 password. For more information, see the Recovery Management for Db2 documentationThe System Resource Recovery panel (ARMDR004) is displayed.

      ARMDR004 === Disaster Recovery - System Resources Recovery ========
      Command ===> _________________________________________________________________
                                                                                    
      Please type in the requested information. Then press Enter.                    
                                                                                    
        Please type in the requested information. Then press Enter.                    
                                                                                    
        Recover RM Repository . . . . . . . 1 1. Yes2. No
        Recover LogMaster Repository. . . . 1 1. Yes2. No
        Recover Work File Database. . . . . 1 1. Yes2. No
        Library that contains DSNTEP2 . . . CSGI,DB2V13M.DSNLOAD___________________
        DSNTEP2 plan name . . . . . . . . . __________  
        Maximum catalog recovery jobs . . . 2___(1-32)
        Image copy type . . . . . . . . . . 1 1. LP 2. LB 3. RP 4. RB
        Synchronization file name . . . . . __________________________________________________________
        Record Validation Report. . . . . . 2 1. Yes  2. No
        Bypass Encryption . . . . . . . . . 2 1. Yes  2. No
        Data Collection dataset name. . . . __________________________________________________________

  2. Specify the information on the panel and then press Enter. (For more information about the entries on this panel, see Field definitions—system resource recovery.)Another System Resources Recovery panel (ARMDR04A) is displayed.

    ARMDR04A ======== Disaster Recovery - System Resources Recovery ====================
    Command ===> _________________________________________________________________
                                                                                  
    Please type in the requested information. Then press Enter.                                                                                      
      Extend Recovery Point at DR. .  2  1. Yes   2. No                            
      Archives Cataloged . . . . . .  1  1. Yes   2. No                            
      Restore archive copies to disk  0  (0 or 1 copy)                             
         Number of logs to disk. . .  ____ Logs __________Hours ________Days                                        
          Restore program. . . . . .  2  1. PACLOG 2. RMGR (ARMBARC)                                                                         
      zIIP Redirection . . . . . . .  1  1. Enabled  2. Disabled
      Initialize Active Logs.. . . .  2  1. Yes   2. No
      Init Actives with DSNJLOGF . .  2  1. Yes   2. No                              
      Maximum log jobs per member. .  1_ (1 - 10)                                  
      Archive copy to use offsite. .  2  1. Offsite Logs 2. Archive 2  3. Archive 1
      BSDS Log Processing Limit. . .  ____  Logs _____Hours  ______Days
      History File Health Check. . .  _  1. Yes2. No
       Email at EOJ. . . . . . . . .  _________ EMAILDST entry
     EOJ RC. . . . . . . . . . .  ____ Range 0-254
       Unrecover RC. . . . . . . . .  Range 0-254    

  3. Specify the information on the panel and then press Enter.For more information about the entries on this panel, see Field definitions—system resource recovery.

    The Disaster Recovery - OffSite Copy Options panel is displayed.

    ARMDR005 = Disaster Recovery - OffSite Copy 1 Options =============
    Command ===> _________________________________________________________________
                                                                                  
    Please type in options for Copy 1                                              
                                                                                  
      Disk unit . . . . . . . SYSALLDA                                             
                                                                                  
      Disk options (optional)                                                      
                                                                                  
        SMS data class. . . .  ________                                            
                                                                                  
        SMS management class.  ________                                            
                                                                                  
        SMS storage class . .  ________                                            
                                                                                  
        Unit count. . . . . .  ________                                            
                                                                                  
      Compression . . . . . .  _  1. Yes  2. No  (Yes requires PACLOG)
  4. Specify the information on the OffSite Copy Options panel, then press Enter. (For more information about the entries on this panel, see Field definitions—offsite copy options.)The Disaster Recovery - System Resources Recovery panel (job card information) is displayed.
  5. Specify the information on the job card information panel, then press Enter. (For more information about the entries on this panel, see Field definitions—job card information.)
  6. At this point, you can generate the JCL to recover system resources, or you can wait until you have also set options for establishing a recovery point and made archive log copies and then generate JCL for all three steps into a single job.
    1. To generate the job now, select 8. Prepare to Recover the DB2 Subsystem (ARMBSRR) and then press Enter to create JCL.
    2. To generate a single job for all three disaster recovery steps set all options, then select 9. Generate ALL Disaster Recovery Jobs, and then press Enter.
  7. When the JCL Specification panel appears, enter a fully qualified output data set name. Be aware of the following information:
    • The output data set is used for saving the JCL and must be cataloged. If not enclosed in quotes, the output data set will be prefixed by your TSO prefix.

    • The job statement must contain a symbolic variable (&#) for the job number. For more information, see Output-data-sets-job-cards-and-symbolic-variables.

      Important

      If you selected Simulate Yes, BMC AMI Recovery Manager appends .SIM to the data set name if the final node does not end in SIM or .SIM. If you are using the Recovery Management for Db2 solution and you selected Estimate Yes, BMC AMI Recovery Manager appends .EST to the data set name if the final node does not end in EST or .EST. You must have created these GDG bases previously.

  8. Save the JCL data set.

This section contains the following topics:


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*