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 recovery simulation JCL to verify that you have all resources required for a system resource recovery. (For additional information, see Recovery-simulation.)
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.)
- 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 that 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 that is established for the offsite JCL.
- 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
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.
To create a system resource recovery job (ARMBSRR)
Start this procedure at the BMC AMI Recovery Manager Main Menu.
- Access the System Resources Recovery panel, as follows:
- Select System Resources
- Select Disaster Recovery Prep
- Select Prepare to Recover the Db2 Subsystem
(
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 documentation).The System Resource Recovery panel (ARMDR004) is displayed.
============ Disaster Recovery - System Resources Recovery ====================
Command ===> _________________________________________________________________
Please type in the requested information. Then press Enter.
Extend Recovery Point at DR. . _ 1. Yes 2. No
Recover RM Repository. . . . . _ 1. Yes 2. No
Recover Log Master Repository . _ 1. Yes 2. No
Recover Work File Database . . 1 1. Yes 2. No
Library that contains DSNTEP2. CSGI.DB2V10M.DSNLOAD________________________
Maximum catalog recovery jobs. __ (1 - 32)
Image copy type. . . . . . . . _ 1. LP 2. LB 3. RP 4. RB
Synchronization file name. . . ____________________________________________
Data Collection dataset name . ____________________________________________
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.
============ Disaster Recovery - System Resources Recovery ====================
Command ===> _________________________________________________________________
Please type in the requested information. Then press Enter.
Archives Catalogued . . . . . . _ 1. Yes 2. No
Restore archive copies to disk 0 (0 or 1 copy)
Number of logs to disk. . . _ Logs ___ Hours ___ Days
Restore program . . . . . . _ 1. Yes 2. No
Initialize Active Logs . . . . _ 1. Yes 2. No
Init Actives with DSNJLOGF . . _ 1. Yes 2. No
Maximum log jobs per member. . _ (1-10)
Archive copy to use offsite. . _ 1. Offsite 2. Archive 2 3. Archive 1
BSDS Log Processing Unit . . . _ Logs __ Hours 29 DaysSpecify 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.
- 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.
- 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.)
- 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.
- To generate the job now, select Option 6, Prepare to Recover the DB2 Subsystem (ARMBSRR) and then press Enter to create JCL.
- To generate a single job for all three disaster recovery steps, set all options, then select Option 9, Generate ALL Disaster Recovery Jobs, and then press Enter.
- 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.
- Save the JCL data set.
Related topics