Generating JCL for local recovery

This process generates JCL to recover the entire Db2 system to an earlier point in time.

The process is intended for a local recovery of a Db2 system that is currently active. It uses a conditional restart of the subsystem followed by recovery of all Db2 data. In addition, it generates revalidation JCL that ensures the recoverability of the objects and produces a report showing objects that were included in the backup, but that no longer exist.

Related topics

ARMBLGR—Log range analysis

Recovery-strategy

BMC AMI Recovery Manager includes batch log range analysis in the JCL it generates to recover the subsystem. Identifying objects that have not changed (XUNCHANGED) between the current time and the recovery point, BMC AMI Recovery Manager can avoid the unnecessary recovery of unchanged objects and can dramatically improve processing time. Be aware that XUNCHANGED processing does not occur for indexes unless they have the COPY YES attribute. For more information about XUNCHANGED processing, see About XUNCHANGED processing in local subsystem recovery. For more information about batch log analysis, see ARMBLGR—Log range analysis.

Important

As a component of the Recovery Management for Db2 solution, BMC AMI Recovery Manager supports conditional restart avoidance for faster, more efficient full subsystem local recoveries.

For more information, see the Recovery Management for Db2 documentation

Before you begin

Make sure you have performed the following tasks:

  • Build application object sets for the subsystem and back them up (see Build subsystem object sets and generate backup JCL). If this was not done prior to the recovery point, this process cannot be used.
  • Set or verify the subsystem options for the utilities you are going to use. For more information, see BMC-AMI-Recovery-Manager-backup-and-recovery-options.
  • Set or verify the BMC AMI Recovery Manager option set information.
  • Ensure that you have authority for the following:
    • EXECUTE authority for the BMC AMI Recovery Manager plan
    • Db2 -ARCHIVE LOG command
    • APF authorization for the following:
      • ARMBSRR
      • ARMBARC
      • ARMBTSI
      • ARMBCRC
      • ARMBGEN
      • ARMBLGR
      • ALPMAIN

To generate JCL for local recovery

Start this procedure at the BMC AMI Recovery for Db2 Main Menu.

  1. Access the Local System Recovery panel, as follows:
    1. Select 6. Subsystem recovery.

    2. Select 4. Local recovery.The Local System Recovery panel (ARMUFS4) is displayed.

      Important

      This panel has different fields if you are using the Recovery Management for Db2 solution password.

      ARMUFS4 ==================== Local System Recovery ============================
      Command ===> _________________________________________________________________
                                                                                    
      Generates JCL to recover active DB2 subsystems at the local site.
                                                                                    
        Object Set owner . . . . . . . . . . . . . . . .  RMD__                        
        Object Set name prefix . . . . . . . . . . . . .  ARMBGPX_________                
        Recover start range. . . . 2022 - 03 - 29 04 . 54 . 59 (YYYY-MM-DD HH.MM.SS)
        Recover end range. . . . . 2022 - 03 - 29 04 . 54 . 59 (YYYY-MM-DD HH.MM.SS)
         
                                                                                   
        Job card data set . . . RDAJLW.ARM.JCL(JOBCARD)___________________________         
        System Resource recovery JCL output                                          
          data set name . . . . . RDAJLW.ARM.JCL(BSRROUT)_________________________         
        Application data set RECOVER JCL output                                      
          data set name . . . . . RDAJLW.ARM.JCL(BSRRAPP)_________________________
        Email at EOJ. . . . . . . __________________________EMAILDST entry name
        EOJ RC. . . . . . . . . . _________________Range 0-254

  2. Enter information as required and press Enter.For more information, see  Local subsystem recovery fields table.

    Another Local System Recovery panel (ARMUFS4A) is displayed.

     ARMUFS4A =================== Local System Recovery =====================
    Command ===> ___________________________________________________________

    Generates JCL to recover active DB2 subsystems at the local site.

    Conditional restart . . . . . . . . . . . . 1 1. Yes 2. No 3. Auto
    Stop DB2 after ARMBSRR executes . . . . . . 1 1. Yes 2. No
    Recover Work File Database. . . . . . . . . 1 1. Yes 2. No
    Library that contains DSNTEP2 . CSGI.DB2V13M.DSNLOAD__________________
    DSNTEP2 plan name . . . . . . . . . . . . . _____________
    Update history file with HISTONLY option. . 1 1. Yes 2. No
    Exclude unchanged from recovery . . . . . . 1 1. Yes 2. No
    Generate ObjectSet syntax . . . . . . . . . 1 1. Yes 2. No
    Record Validation Report. . . . . . . . . . 1 1. Yes 2. No
    Bypass Encryption . . . . . . . . . . . . . 2 1. Yes 2. No   
    Simulate recovery . . . . . . . . . . . . . 2 1. Yes 2. No
    Include Clones. . . . . . . . . . . . . . . 2 1. Yes 2. No
    data set name . . . . ________________________________

  3. Enter information as required and press Enter.

    Important

    For more information, see Local subsystem recovery fields table.

  4. On the JCL Specification panel, 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 the output JCL data set is a GDG, the product always uses SYS1.MODEL as the model data set name.

  5. Save the JCL data set or submit the job as required.

The following table describes the local subsystem recovery fields: 

Field

BMC AMI Recovery Manager   default

Description

Object Set owner

Last value used

Specifies a valid TSO user ID to be used by BMC AMI Recovery Manager as the creator_ID part of each object sets name

For more information about authorization for creating object sets, see Object set authorization.

Object Set name prefix

Last value used

Specifies a character string to be used by BMC AMI Recovery Manager as a prefix in the object sets part of each object set name

Important

Delimited entries are not allowed for the object set name prefix.

Recover start range

Recover end range

Current time

Specifies the recovery time in the format yyyy-mm-dd hh.mm.ss

If entered, you should choose a time prior to current for the start range.

Job card data set

Last value used

Specifies a fully-qualified name of the data set containing job card information

The job name must contain the symbolic variable &##.

System Resource recovery JCL output data set name

Last value used

Specifies a fully-qualified name of a new or existing data set to be used for saving the recovery JCL for the system resources (catalog and directory)

Application data set RECOVER JCL output data set name

Last value used

Specifies a fully-qualified name of a new or existing data set to be used for saving the application data set recovery JCL

Email at EOJ / EOJ RC                                           

None

Specifies entry name in the EMAILDST member to request email notification when ARMBSRR completes with a return code greater than or equal to the EOJ_RC.

Important

Email entry has a name up to 8 characters in length, and follows the same rules of a PDS member name and return code valid input is 0-254.

Sample for Email entry in the EMAILDST (email distribution) member in the CNTL data set:

email entryname.CLASS jes2 output class                            
email entryname.SMTP external writer or CSSMTP application         
address space                                                      
email entryname.HELO domain name of the sending host               
email entryname.MAIL FROM: must be in valid email address format   
email entryname.RCPT TO1: must be a valid email address            
email entryname.SUBJECT: subject line                   

Conditional restart

None

Controls whether the generated recovery is a conditional restart or to a log point with the CONDRESTART syntax. The following options are available:

Option

Description

YES

Generates a conditional restart recovery and the ALPMAIN step is not be generated. Enter 1 for CONDRESTART YES.

NO

Requires a recovery to a log point. Enter 2 for CONDRESTART NO.

AUTO

Generates a recovery to log point if possible or a conditional restart if necessary. Enter 3 for CONDRESTART AUTO.

Important

  • CONDRESTART NO and AUTO require a solution password and use BMC AMI Log Master (ALPMAIN) to find DDL and quiet points.
  • BMC AMI Log Master for Db2 determines if DDL activity exists for the Db2 Catalog and Directory and if any quiet points are found for the specified recovery range.

Stop DB2 after ARMBSRR executes

Yes

Controls whether a step is generated to STOP DB2 after program ARMBSRR generates JCL to recover the subsystem.

If you select No for this option, you must manually STOP DB2 before running the recovery.

Recover Work File Database

Yes

Recovers the work file database during subsystem recovery

If you choose not to recover the work file database, this step is omitted from the recovery job.

Library that contains DSNTEP2

Yes

Specifies the library that contains DSNTEP2

Tip

We recommend that you choose No if your DSNLOAD library does not contain DSNTEP2.

DSNTEP2 plan name

(BMC.DB2.SPE2304)

DSNTEP2

Specifies the plan name for the DSNTEP2 program.       

If you do not use this option, ARMBSRR searches for the DSNTEP2 plan name in the POF (product options file).

To register the DSNTEP2 plan name in the POF, specify one of the following options:

For the SSID level, ssid.DSNTEP2PLAN=planName
For the global level, DSNTEP2PLAN=planName

Rules for naming Plan name

  • A plan name cannot be longer than eight characters.
  • The plan name character must be either a letter or one of the following three special characters: #, @, $.
  • The remaining seven characters can be letters, numbers, or one of the following special characters: #, @, or $.
  • A plan name cannot contain a hyphen (-).
  • A plan name cannot contain quotes (' ') or (" ").
  • A plan name cannot contain accented characters (à, é, è, and so on).

Update history file with HISTONLY option

Last value used

Captures the copy information for the Db2 spaces DSNDB06.SYSCOPY, DSNDB01.DBD01, DSNDB01.SYSDBDXA, and DSNDB01.SYSUTILX in the BMC AMI Recovery Manager archive history file without copying the archive logs

BMC AMI Recovery Manager stores image copy registration information from the log in the archive history file so that it can optimize recovery JCL for the catalog and directory. The default value is No.

Important

Use this option if you made images copies of the catalog and directory within the log range of the log just archived. In this case, the history file does not yet contain a record of those copies.

Exclude unchanged from recovery

No

Excludes unchanged spaces from recovery

The objects that are marked as UNCHANGED are excluded from the recovery JCL. Objects in WRITE PENDING status are included in the recovery even if they are still marked as UNCHANGED. This option can significantly reduce the time required for recovery by eliminating unnecessary processing.

Generate ObjectSet syntax    

Yes

Specifies whether BMC AMI Recover is to use the repository to identify the objects in the object set, which means that you do not need to regenerate the recovery JCL when objects in the object are set to change. BMC AMI Recovery Manager generates the TABLESPACE OBJECTSET option and the INDEX OBJECTSET option in the recovery JCL.

Record Validation Report

(BMC.DB2.SPE2210)

Yes

Writes the validation report to the RECOVERY_EXCEPTIONS table. You can view the contents of the RECOVERY_EXCEPTIONS table in Command Center 

Valid values for Record Validation Report are as follows:

YES—(Default) Writes the validation report into the RECOVERY_EXCEPTIONS table. 
NO— Disables inserts into RECOVERY_EXCEPTIONS table regardless of whether solution password exists or not.

Bypass Encryption

(BMC.DB2.SPE2210)

No

Checks whether the object is encrypted or not. The BMC AMI Recovery Manager system resources recovery performs this check by default.

Valid values for Bypass Encryption are:

  • YES—Bypasses encryption checking done by system resources recovery and disables encryption checking inserts into RECOVERY_EXCEPTIONS table.
  • NO—(Default) Checks encryption for objects required for system resources recovery.   

Simulate Recovery

No

Simulates recovery at the local site and provides a way to help you prove that you can recover the Db2 data without performing an actual recovery.

You can use recovery simulation to verify that needed recovery resources are valid and available and that log apply can be done. This option is a feature of the Recovery Management for Db2 solution only, and both the BMC AMI Recovery Manager and BMC AMI Recover components of the Recovery Management for Db2 solution are required. For more information, see the Recovery Management for Db2 documentation

Include Clones

No

Specifies whether to create JCL to recover the cloned objects in the object sets being created

Cloned objects are recovered separately from base objects. This option is not valid with compatibility mode.

If you use clones, you need to be sure to specify Yes. Specifying Yes generates a separate ARMBGEN step for generating application recovery for only cloned objects. After the system recovery runs, the ARMBGEN JCL runs, which generates JCL to recover the applications. Be sure to run both jobs that are generated--for regular objects and for clones.

Output data set (for clone object sets)

None

Specifies the name of an existing data set where you want to place the recover JCL for the cloned objects

This must be a fully qualified data set name that does not contain quotes.

 

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