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.

Creating object sets with ARMBGRP

Use the CREATE OBJECTSET command to create an object set based on exceptions, indexes, index space names, plans, packages, storage groups, user-defined SQL, table name, table spaces, or volumes.

You can optionally copy an existing object set in order to retain the same backup and recovery options and authorizations.

With dynamic object sets, you can create an empty object set (a object set for which no objects are found that meet the definition). After you create the objects and then open the object set, the object set is automatically populated. This ability enables you to prepare to back up and recover objects that do not yet exist. For example, if you know that a new application is being added to your system, you can set up the object sets in advance. When the objects are created, dynamic object sets will automatically find and add them to the backup and recovery jobs.

Important

Object sets created by volume are static object sets, not dynamic object sets. Object sets created by exception are static object sets by default, but when creating object sets online or in batch using INCLUDE EXCEPTION, you can specify DYNAMIC to enable dynamic object sets. For example, to enable dynamic object sets, you can use the following syntax:

//ARMIN     DD *                 
  CREATE OBJECTSET USERID.EXCEPTION
     DESCRIPTION 'EXCEPTION STATUS OBJECTS'
     REPLACE YES                 
     INCLUDE EXCEPTION                   
       DYNAMIC                  
       RECOVERYPEND
       CHECKPEND
       COPYEND
       LPL
       STOPPENDERRORRANGE                                                            
/*

With BMC AMI Recovery Manager version 11.1 and later, you can use multiple INCLUDE statements in the CREATE OBJECTSET syntax. For example, you can use the following syntax:

//ARMIN     DD *                 
  CREATE OBJECTSET RDAJTR.TEST_BYDEF2
     REPLACE YES                 
     DESCRIPTION 'CREATE BY DEF '
     INCLUDE TABLE                   
       JTR.T40N                  
     INCLUDEIX NO                
     INCLUDE TABLESPACE              
       ARMDBJTR.TS40P1           
     INCLUDEIX NO;               
   ...
   ...
   ...                                                
/*

Important

You cannot use the INCLUDE VOLUMES option multiple times. INCLUDE EXCEPTION is also not allowed multiple times unless you have enabled dynamic object sets.

Unicode support

BMC AMI Recovery Manager supports Db2 objects with Unicode names, both those that can be translated to EBCDIC and those that cannot.

BMC AMI Recovery Manager online panels and reports make use of EBCDIC characters. Any Unicode characters that cannot be translated into EBCDIC are represented with hexadecimal substitution characters.

About table space table index exception and volume object sets

For object sets made via table space name pattern, table name pattern, index name pattern, and exception status, ARMBGRP performs a Db2 catalog search.

For volume object sets, ARMBGRP supports two different methods of obtaining information. You can create the object set by performing catalog searches or by using the volume’s VSAM volume data set (VVDS).

  • Catalog search method

    The catalog search method uses the Db2 and Integrated Catalog Facility (ICF) catalogs to locate the Db2 objects for the desired subsystem or data sharing object set. This method does not require the volume to be online and can be executed after a volume failure has occurred. This method is ideal for an ad hoc recovery after an unexpected volume failure.

  • VVDS method

    The VVDS method uses the VSAM 'table of contents' located on the volume and the Db2 catalog to identify objects that belong to the specified Db2 subsystem or data sharing object set. This method requires the volume to be online and available at the time that the job executes.

    Warning

    Recovering with a object set that was created by the VVDS method does not include objects that were created or moved to the volume after the object set was generated.

Important

Creating a volume object set interactively can take significantly longer than using the batch process. The interactive process assumes that the volume is available and searches the operating system and Db2 catalogs for the required information.

About user-defined SQL object sets

For object sets created using user-defined SQL, BMC AMI Recovery Manager uses the ARMSQL DD statement and the INCLUDE SQL syntax.

For more information about the ARMSQL DD statement, see Specifying the ARMBGRP data set DD statements.

For more information about the INCLUDE SQL syntax, see CREATE-OBJECTSET.

BMC AMI Recovery Manager also enables you to enter dynamic SQL inline in the INCLUDE SQL syntax between the #BEGINSQL and #ENDSQL options. You can enter multiple INCLUDE SQL statements with the inline SQL in a CREATE OBJECTSET statement.

The INCLUDE SQL syntax supports a limited number of key words for including related objects. Sub selects are supported. The same SQL restrictions apply in batch as in the online object set creation by SQL (Creating-new-object-set).

About repository object sets

Use the INCLUDE REPOSITORY option to create an object set containing the repository objects of BMC AMI Recovery Manager (with R+/CHANGE ACCUM and Log Master, if they are present in your system).

BMC AMI Recovery Manager obtains the tables and indexes that make up the repository of each product from the plan listed in the option file of each product.

The default option file names for each product are as follows:

  • ARM$OPTS (BMC AMI Recovery Manager)
  • AFR$OPTS (BMC AMI Recover)
  • ALP$OPTS (Log Master)

Creating a repository object set can streamline the backup and recovery of the repositories, especially if you are using BMC AMI Copy or Online Consistent Copy as the backup utility. BMC AMI Recovery Manager uses the OBJECTSET option of BMC AMI Copy, which means that you do not need to regenerate the backup JCL when objects in the object set change. For more information, see OBJECTSET-support.

Important

If you change the plan names for BMC AMI Recovery Manager, Log Master, or R+/CHANGE ACCUM, you should rebuild the repository object set to prevent problems from occurring.

Also, when you migrate to a new version of Db2, you need to create new repository object sets to backup the objects of the repository.


Related topic

About-ARMBGRP





 

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