Using BMC AMI Recovery Manager object sets

You can set up object sets in the BMC AMI Recovery Manager for Db2 (BMC AMI Recovery Manager)product. BMC AMI Recover allows you to identify both table spaces and index spaces in groups for processing by BMC AMI Recover.

Using dynamic grouping, BMC AMI Recover reads the objects in the group each time you run the BMC AMI Recover job, so objects might be added or removed from the group between BMC AMI Recover job runs.

Related topics

Table-space-specification

Single-index-specification

Multiple-index-specification

LOGSCAN-command

Important

BMC AMI Recover does not read BMC AMI Recovery Manager recovery options for the group. If BMC AMI Recovery Manager recovery options change, you must run BMC AMI Recovery Manager to pick up the new options and generate the control cards.

After the group is defined using BMC AMI Recovery Manager, BMC AMI Recover uses the BMC AMI Recovery Manager repository and the BMC Common Db2 repository to identify the objects in the group. BMC AMI Recover uses the objects directly from the repository tables. The objects in the group are kept up to date with dynamic grouping.

Dynamic grouping resolves the table space and index object names for inclusion with the BMC AMI Recover commands that support group object types.

BMC AMI Recover provides the OBJECTSET syntax to specify a group. The long-range plan is that OBJECTSET will be used as a common syntax by other BMC utilities for Db2. You can use OBJECTSET with the following BMC AMI Recover commands:

IMPORT
LOGSCAN
MIGRATE
RECOVER
REBUILD INDEX
SIMRCVR
SIMBLD INDEX

For more information, see the syntax descriptions for each command in Command-and-syntax-reference, and specifically, OBJECTSET-specification.

Following are some examples of the use of the OBJECTSET syntax:

Syntax	Objects copied
RECOVER OBJECTSET creator. name¹	Recovers all objects in the object set-table spaces and indexes Note that INDEXES YES is not valid with this specification.
RECOVER TABLESPACE OBJECTSET creator. name¹	Recovers only table spaces in the object set except for those table spaces named in the EXCLUDE statement
RECOVER TABLESPACE OBJECTSET creator. name INDEX YES¹	Recovers table spaces in the object set along with their associated indexes, regardless of whether the indexes are included in the group You can use the EXCLUDE statement to ignore one or more table spaces and their associated indexes.
RECOVER INDEX OBJECTSET creator. name¹	Recovers only indexes in the object set except for those indexes named in the EXCLUDE statement
REBUILD INDEX OBJECTSET creator. name²	Rebuilds all indexes in the object set except for those indexes named in the EXCLUDE statement
LOGSCAN OBJECTSET creator. name	Log scan processing of all objects in the object set-table spaces and indexes
LOGSCAN TABLESPACE OBJECTSET creator. name	Log scan processing for only table spaces in the object set
LOGSCAN TABLESPACE OBJECTSET creator. name INDEX YES	Log scan processing for table spaces in the object set along with their associated indexes, regardless of whether the indexes are included in the group
LOGSCAN INDEX OBJECTSET creator. name	Log scan processing for only indexes in the object set

^{1 SIMRCVR is also valid.}

^{2 SIMRBLD is also valid.}

Important

DSNUM cannot be used with OBJECTSET. The DSNUM used for each object is its DSNUM in the repository.

When you use OBJECTSET, if BMC AMI Recover tries to recover a group of objects and more than 10 of the objects are unrecoverable, BMC AMI Recover issues an error for each object that is unrecoverable, and discontinues further processing of the group. This behavior is based on the ERRCONT option which has a default value of 10. To avoid this behavior, set the ON ERROR CONTINUE option with a value that will exceed the possible number of errors in the group, and the recovery will be complete.

For more information about grouping in BMC AMI Recovery Manager, see the BMC AMI Recovery Manager for Db2 documentation.

Using BMC AMI Recovery Manager object sets

On this page