Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Recovery Manager for Db2 13.1.

General recovery options

Fields on the General Recovery Options panel apply to all supported recovery utilities.

Those fields are listed alphabetically in the following table along with the corresponding BMC AMI Recovery Manager defaults.

For additional information about any of the utility options, see the following or the IBM Db2 command and utility reference as appropriate: 

General recovery fields

Field

BMC AMI Recovery Manager default

Description

Always rebuild indexes

No

Specifies whether rebuild indexes from table data or to recover them from image copies and log data, as follows:

Yes—rebuilds all indexes from table data, even if an image copy and log data are available.

No—attempts to recover indexes from image copies and log data when possible. Any index that cannot be recovered is automatically rebuilt.

Important

When used with BACKOUT YES or AUTO, BMC AMI Recovery Manager automatically resets this option to No and issues a warning message.

Allocate in KILOBYTES

No

Converts cylinder or track specifications to kilobytes when you redefine VCAT objects

Used in conjunction with Redefine VCAT objects.

Check pend action

None

Specifies the action to correct check pending status on recovered spaces after a point-in-time recovery, as follows:

  • Check—run the specified check utility to correct check pending and auxiliary warning (AUXW) status
  • Repair—run the REPAIR utility to turn off check pending and AUXW status
  • None—no action

Check utility

DB2 CHECK

Specifies either the BMC CHECK PLUS utility or the IBM Db2 CHECK (DSNUTILB) utility for performing integrity checks on the current object set or object

Copy after (post-recovery)

No (all types)

Specifies a copy type to make after the recovery is complete, as follows:

  • LP— makes a primary image copy b for the local site after the object set or object has been recovered.
  • LB—makes a backup image copy for the local site after a object set or object has been recovered. If you select this option, you must also specify an LP copy.
  • RP—makes a primary image copy for the recovery site after the object set or object has been recovered.
  • RB—makes a backup image copy for the recovery site after the object set or object has been recovered. If you select this option, you must also specify an RP copy.

Copy utility

DB2 COPY (DSNUTILB)

Specifies either the BMC AMI Copy utility or the IBM Db2 COPY (DSNUTILB) utility for making post-recovery image copies immediately after the current object set or object has been recovered

Data set sizing

Catalog

Sizes objects when generating JCL, as follows:

  • Catalog—use the Db2 and ICF catalog information for sizing purposes at the time of JCL generation. This method requires sizing calculations at the time of JCL generation.
  • Defaults—use existing default sizing information from the Work File options established in the Recovery options.
  • BMCSTATS—use statistics from the BMCSTATS tables. Statistics in the BMCSTATS table are collected by DASD MANAGER PLUS and optionally by BMC AMI Copy.

For more information on data set sizing see Data set sizing.

Important

Although the Data Set Sizing option is located with the General Recovery Options, it is also used when generating backup JCL when the copy utility is anything other than BMC AMI Copy.

Delete STOGROUP objects

No

Deletes STOGROUP 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 information:

  • If you specify SITETYPE RECOVERY, the product forces the option Delete STOGROUP objects to Yes.
  • Specifying Delete STOGROUP objects to Yes causes the data set to be deleted if the object is STOGROUP-defined, regardless of the setting of the REUSE parameter.

Limit SYSCOPY search

0

Limits the number of days of records to search in the SYSIBM.SYSCOPY table when looking for a requested copy or quiesce point

Limiting SYSIBM.SYSCOPY searches avoids unneeded I/O operations, excessive memory use, and improves performance.

0—search all rows in the SYSCOPY catalog table

1 through 99—number of days of SYSCOPY entries to include in the search.

Max concurrent jobs

1

Specifies the maximum number of concurrent jobs to process the current object set.

Warning

Do not specify a value that is higher than the available number of initiators. Doing so could cause an unending wait situation.

Mirroring

No

Specifies that the objects in the object set are mirrored and that the mirrors are considered to be valid backups at the disaster recovery site

In order to use this option, you must have set at least mirroring Level 2 (BSDS, active logs, and catalog and directory) in the subsystem-level General Recovery Options.

This option is only available if you are setting recovery options for a object set and using the Recovery Management for Db2 solution.

Recover utility

BMC AMI Recovery ManagerR only:

DSNUTILB

Recovery Management:

BMC AMI Recover

Specifies either BMC AMI Recover or IBM Db2 RECOVER (DSNUTILB) to recover the current object set or object.

Important

You must select BMC AMI Recover to use recovery simulation.

Redefine VCAT objects

No

Includes IDCAMS delete and define steps for VCAT spaces before the recover utility executes

Be aware of the following information:

  • To use this option, you must have Db2 STOP and DISPLAY authority and control authority on the physical data sets.
  • If you specify SITETYPE RECOVERY, the product forces the option Redefine VCAT objects to Yes.
  • If you specify RSITEDELDEF=NO in the option set and SITETYPE = RECOVERY and JCLTYPE = LOCAL in the options statement, the product does not generate the IDCAMS delete and define steps for VCAT or STOGROUP objects. For more information, see Option-sets-and-configuration-options.
  • 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 Recover 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 BMC Common Db2 repository, the BMC AMI Recovery Manager repository, and the CHANGE ACCUM repository), ARMBSRR issues an error message and fails.

Region Size

0 MB

Specifies the amount of virtual storage used by the recover utility. The default value is 0 MB. The valid range is -1 through 2047 MB.

A value of -1 specifies that BMC AMI Recovery Manager will not generate region size at the step level.

Important

For best performance, we recommend a region size of 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 typical BMC AMI Recover step requires between 5 MB and 8 MB of virtual storage for code, control blocks, and I/O buffers.

REUSE

Yes

Rreuses target spaces, as follows:

  • No—delete and redefine the target spaces.
  • Yes—reuse those spaces without deleting or redefining.
  • NOSCR (NOSCRATCH)—avoids running IDCAMS

Use INDEX ALL recover

No

Specifies whether to automatically rebuild all indexes for the table spaces in the object set

When using this option, you do not need to explicitly include the indexes in the object set and the ARMBGEN program does not need to search for related indexes during JCL generation because they will be rebuilt.

This option is intended for applications having a large number of indexes (for example, full subsystem applications such as SAP).

Warning

You must verify that the primary and secondary allocations in the work file options of the object set are large enough to accommodate the object set. Do not use this option if any of the following conditions are true:

  • The object set explicitly includes indexes
  • The object set was created by partition
  • The object set contains mirrored indexes

See Symbolic-variables-in-post-recovery-image-copy-data-set-names for more information.


Related topics

Authorization to use delete and redefine recovery options

Multiple-job-optimization

Recovering-object-sets

Responding-to-unsatisfactory-object-status

Task-7-Generating-application-recovery-JCL-ARMBGEN



 

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