Before using BMC AMI Recovery Manager

Adding a Db2 subsystem to BMC AMI Recovery Manager

When you install BMC AMI Recovery Manager for the first time, the BMC Installation System:

• Generates the BMC AMI Recovery Manager option set (the ARM$OPTS file)
• Creates the repository tables for the specified Db2 subsystem
• Creates synonyms to R+/CHANGE ACCUM and Log Master if required

To add a subsystem to BMC AMI Recovery Manager after the initial installation, see the Installation System documentation.

BMC AMI Recovery Manager and PACLOG option set considerations

BMC AMI Recovery Manager and PACLOG use the Db2 Product Configuration technology (LGC) for option sets.

Option sets provide values for the configuration options for BMC AMI Recovery Manager and PACLOG. The default option sets are

• ARM$OPTS for BMC AMI Recovery Manager
• ALM$OPTS for PACLOG

You should set the option values in ARM$OPTS and ALM$OPTS to the same values for an SSID.

Using the same values in the option sets ensures that both products use the same archive history file, time stamp value, and work data sets, all of which are specified in the option sets.

Alternatively, you can use a product options file (POF) instead of BMC Db2 Component Services (DBC) and BMC Db2 Product Configuration (LGC) technology to manage BMC AMI Recovery Manager product options.

Sharing BMC tables

BMC AMI Recovery Manager shares tables with other BMC products. For example, BMC AMI Recovery Manager uses the BMCLGRNX table during recovery point analysis and the BMCXCOPY table for index backups and Instant Snapshot copies.

The following tables should be shared with other BMC products:

• BMCUTIL
• BMCSYNC
• BMCXCOPY
• BMCLGRNX

Sharing solution common code (SCC)

The Solution Common Code (SCC) is a component of BMC AMI Recovery Manager.

SCC is a supporting software component that provides common processes for several BMC products for Db2. The SCC component requires no action from you except when maintenance is required. You can view the version of the SCC code on BMC AMI Recovery Manager reports or by selecting the About option on the BMC AMI Recovery Manager Main Menu. You can also see a list of applied fixes by using the About option on the BMC AMI Recovery Manager Main Menu.

Setting up Db2 object set attach names

If you are operating in a data sharing environment, you can define Db2 object set attach names during BMC AMI Recovery Manager installation. You must also define other control information before you can use those object set attach names.

Creating required temporary tables

BMC AMI Recovery Manager requires declared Db2 global temporary tables and uses them when working with object sets and in several other functions throughout the product.

Db2 Solution Common Code (SCC) also uses global temporary tables for dynamic object sets.

To ensure that you have enough space allocated for processing, set up the temporary tables, as follows:

• Db2 Version 10 and Db2 Version 11 systems

Db2 uses the work file database to dynamically allocate the global temporary tables. For each Db2 subsystem and for each member of a Db2 data sharing system, you must ensure that the work file database contains at least one Db2 storage-group-defined table space with a page size of 32 KB.

IBM recommends that at least one 32 KB storage-object-set-defined table space be defined for global, temporary tables, and indexes. (See information for a new zparm WFDBSEP in IBM APAR PM02528 WORKFILE DATABASE USABILITY ENHANCEMENT.)

Preparation for archive logs greater than 64K tracks

The following procedure describes preparation for archive logs greater than 64K tracks.

To successfully use archive logs greater than 64K tracks which are available with Db2, you must set up some SMS rules.

1. Create an SMS DATACLAS with a Data Set Name Type LARGE. This value assigns a DSORG type of PS-L to the data set. The simplest way to accomplish this is to make assignments based on a data set name filter. For example:

   WHEN (&DSN = DSNDXW.DXW2.ARCLG1L.A0*)      
       SET &DATACLAS = 'DCLARGE'

2. Create a DATACLAS rule to accommodate the temporary files created by some BMC AMI Recovery Manager programs when processing archive logs. These files are identified with .Z0* and should also be allocated as DSNTYPE=LARGE. For example:

   WHEN (&DSN = DSNDXW.DXW2.ARCLG1L.Z0*)      
       SET &DATACLAS = 'DCLARGE'

3. The archive log files and the temporary files can be extremely large, so you might want to set up a STORCLAS rule and a STORGRP rule to direct the data sets to a specific SMS Storage group. For example:

   WHEN (&DATACLAS = 'DCLARGE')  
       SET &STORCLAS = 'DXWSMS'

   and

   WHEN (&STORCLAS = 'DXWSMS')   
       SET &STORGRP = 'DXWSMS'

Safeguarding the repository

You should make backup copies of the repository table spaces as soon as possible after installing BMC AMI Recovery Manager.

You can use the online interface to create the JCL to do this (Creating a repository object set for backup or recovery). You should continue to make backups at intervals that are compatible with your standard practices.

In the event of a Db2 failure that involves the repository, you can continue to use BMC AMI Recovery Manager to create object sets and generate JCL. However, you cannot save object set information or retrieve information that has already been saved until the repository failure is resolved.

When you perform a recovery at a disaster recovery site, you must recover objects in the correct order. Use the ARMBSRR program to make available and to recover the catalog and directory, the repository, and the R+/CHANGE ACCUM repository in the correct sequence. For more information, see Recovering-from-a-Db2-system-disaster and ARMBSRR—System resource recovery.

This section contains the following topics: