Recovery utility options

Choose either the BMC AMI Recover utility or IBM Db2 RECOVER (DSNUTILB) utility for recovering the current object set or object. Specify the recover utility to use for recovery, as follows:

• AFRMAIN—BMC AMI Recover
• DSNUTILB—DSNUTILB RECOVER

Choose either the BMC AMI Copy utility or IBM Db2 COPY (DSNUTILB) utility as the utility to be used for making post-recovery image copies immediately after the current object set or object has been recovered. Specify the copy utility as follows:

• ACPMAIN—BMC AMI Copy
• DSNUTILB—DSNUTILB COPY

Specify the amount of virtual storage used by the recover utility. The valid range is -1 through 2047 MB.

The default value is 0 MB, in which case the amount of virtual storage needed to run the job is automatically made available when the recover utility runs. Some data centers do not allow a region size of 0 MB.

A value of -1 specifies that BMC AMI Recovery Manager will not generate region size at the step level. BMC AMI Recovery Manager JCL generation recognizes the -1 value and does not generate REGION=.

Specify the action that you want to take to correct-check the pending status on recovered spaces after a point-in-time recovery. You can specify one of the following commands:

• CHECK—run the specified check utility to correct the check pending status
• REPAIR—run the REPAIR utility to turn off check pending status
• NONE—take no action
• RESET—causes the option to default to the value set at the subsystem level. If no subsystem value exists, the option defaults to the product level.

Table spaces that have parents or hash tables will be selected to have CHECK DATA after they are recovered and when the object set option Check Pend Action is CHECK.

Include IDCAMS delete and define steps for VCAT spaces before the recover utility executes. To execute recovery JCL that includes this step, you must have Db2 STOP and DISPLAY authority and control authority on the physical data sets.

Be aware of the following items:

• If you specify SITETYPE RECOVERY, the product forces the option to YES.
• BMC AMI Recovery Manager cannot perform delete and define steps for VCAT-defined spaces that do not have ICF catalog data (for example, objects that have been deleted or migrated). For those objects, BMC AMI Recovery Manager performs one of the following actions:
  • For user-defined VCAT objects, ARMBGEN issues a warning message and generates JCL with the delete and define steps commented out. You can manually retrieve the object, then alter the JCL to include the delete and define statements.
  • For system VCAT objects (such as the Db2 catalog and directory, the repository, and the R+/CHANGE ACCUM repository), ARMBSRR issues an error message and fails.

Specify the maximum number of concurrent jobs that you want BMC AMI Recovery Manager to use when processing the current object set. The range is 0-99.

Choose to either rebuild indexes from table data or to recover them from image copies and log data when possible.

• YES—Rebuilds all indexes from table data, even if an image copy and log data are available.

• NO—(Default) Attempts to recover indexes from image copies and log data when possible. Any index that cannot be recovered is automatically rebuilt.

  For BACKOUT recoveries, BMC AMI Recovery Manager changes this option to NO and issues a warning message.

Recover all indexes for the table spaces in the object set by using INDEX ALL syntax. This option is intended for applications having a large number of indexes (for example, ERP applications such as SAP/R3).

When you select the INDEX ALL option, the ARMBGEN program does not search for related indexes for objects in an object set during JCL generation because their inclusion is implied.

Specify whether the objects in the object sets are mirrored. Mirrored object sets are excluded from the primary disaster recovery JCL that you generate, although they can optionally be included in alternate JCL. This feature is only available with the Recovery Management for Db2 solution and you must activate at least level 2 mirroring at the subsystem level. For more information, see the Recovery Management for Db2 documentation

Limit the time range for which BMC AMI Recovery Manager searches the SYSIBM.SYSCOPY table for a requested copy or quiesce point. Type 0 to search all rows in the SYSCOPY catalog table. To limit the search (for performance reasons), type a value from 1 through 99 to indicate the number of days of SYSCOPY entries to include in the search.

Specify whether the BMC AMI Recover needs to keep ACHK/CHKP status to base or auxiliary space if recovered without their associated spaces. Specify one of the following options:

• YES—(Default) Keep the ACHK/CHKP status to base or auxiliary space if recovered without their associated spaces.
• NO—Do not keep the ACHK/CHKP status to base or auxiliary space if recovered without their associated spaces.