Task 1: (first time only) Building subsystem object sets

To build subsystem object sets

1. In the BMC AMI Recovery for Db2 Main Menu, select option 6. Subsystem recovery and press Enter

2. In the System Recovery Preparation and JCL Generation panel, select Option 1, Full Recovery, and press Enter.The Build Recovery Object Sets panel is displayed.

   ARMUFS1 ==================== Build Recovery Object Sets ============================
   Command ===> _________________________________________________________________
                                                                                 
   You are about to generate JCL to build RMGR recovery object sets based on a sizing balance. Enter the fields and press Enter.         
                                                                                 
     Object Set owner . . . . . . . . . . . . . . RDAXXX__                             
     Object Set name prefix . . . . . . . . . . . ALLOBJ__________                     
     Object Set description . . . . . . . . . . . _________________________            
     Maximum number of object sets. . . . . . . . 10  (2-99)                           
     Object Set by part . . . . . . . . . . . . . 2   (1=Yes/2=No)
     Build job for backup JCL generation. . . . . 1   (1=Yes/2=No)                     
       Output data set. .  ______________________________________
       Copy All Index Spaces . 2 (1=Yes/2=No/3=Auto)                          
          Index Size Threshold __________ _ max bytes(4294967295K,4194303M,4095G)
     Include Clones. . . . . . 2 (1=Yes/2=No)                                   
       Output data set. .  ______________________________________________________
3. On the panel, enter information as required and press Enter.See the following table for descriptions of the fields.
4. When the JCL Specification panel appears, 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.

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

   Important

   BMC AMI Recovery Manager automatically adds EXCLUDE statements for the BMC AMI Recovery Manager and R+/CHANGE ACCUM repositories.

   The subsystem object sets are created and saved in the BMC AMI Recovery Manager repository with GENERATED BY ARMBGPS as the description. Subsystem-object-set-creation-JCL provides an example of the JCL that is generated.

   Option	BMC AMI Recovery Manager default	Description
   Object Set owner	None	Specifies a valid TSO user ID for BMC AMI Recovery Manager to use as the creatorId part of each object set name. For more information about authorizations for creating object sets, see the BMC AMI Recovery Manager for Db2 documentation.
   Object Set name prefix 1	None	Specifies a character string for BMC AMI Recovery Manager to use as a prefix in the object set part of each object set name. BMC AMI Recovery Manager adds a 2-digit number suffix to provide a unique name for each object set. The prefix must not exceed 16 characters. The numerical suffixes that BMC AMI Recovery Manager adds start at 01 and continue up to the value that you provide at the Maximum number of Object sets prompt.
   Object Set description	None	Specifies a description for your object sets. For example, DR SIMULATION.
   Maximum number of object sets	10	Specifies the maximum number of object sets (2-99) to create.
   Build job for backup JCL generation	Yes	Specifies whether to build backup jobs for your applications. Specify No for simulations and estimations. You should already have backups of your business applications.
   Output data set	None	Specifies an output data set for backup jobs. Important Object sets name prefixes cannot be delimited. Leave this blank. You should not be generating backup jobs during a simulation or estimation.
   Copy All Index Spaces	No	Specifies whether to back up eligible index spaces. This option is only available when Some content is unavailable due to permissions. is selected as the recovery utility and Some content is unavailable due to permissions. is selected as the copy utility. Yes—Back up all eligible indexes No—(the default) Do not back up eligible indexes Auto—Back up indexes as large or larger than the size specified in the Index Size Threshold field.
   Index Size Threshold		Specifies the size threshold at which indexes are backed up rather than rebuilt. This option is used in conjunction with Copy Index Space Auto. Enter the size as follows: M—Megabytes (the default). The valid range is 0-4194303. K—Kilobytes. The valid range is 0-4294967295. G—Gigabytes. The valid range is 0-4095.
   Include clones		Specifies whether to create JCL to back up the cloned objects in the object sets being created. Cloned objects are backed up separately from base objects. This option is available only when running on Db2 Version 9 or later and is not valid with compatibility mode.
   Output data set		Enter the name of an existing data set where you want to place the backup JCL for the cloned objects. This must be a fully qualified data set name that does not contain quotes.

   ^{1This task creates object sets in your BMC AMI Recovery Manager repository. If you want to keep your simulation object sets separate from your production disaster recovery object sets, give them a different name.}