Share This:

In a previous article, we introduced the repositories the BMC products use. In that article we spoke about the most important and used of those repositories: The BMC Common utility tables.


In this new article on the same topic we will briefly describe the BMC Common DB2 repository.


The BMC Common DB2 repository was added in December 2009 to the 9.2 version of the Backup & Recovery set of products, in order to support Dynamic Grouping.


In this version, a new way of creating groups of objects (called Object Sets) was introduced. An object set is a set of table spaces and indexes (usually belonging to the same application) that are grouped together in order to perform common backup and recovery procedures. Grouping simplifies the backup and recovery process because you can use the generated JCL to back up or recover the entire group at once. Grouping also simplifies the specification of backup and recovery options, because you can specify the options just once for the entire group.


These Objects sets can be build by using the Recovery Manager for DB2 online interface or by using the Recovery Manager for DB2 batch utilities. Using the batch program is faster for creating groups that contain more than a few hundred objects.


These objects sets could use several patterns to identify objects to INCLUDE or EXCLUDE from the group:


_ TS (table space name pattern)

_ IX (index name pattern)

_ TB (table name pattern)

_ IS (index space name pattern)

_ PL (plan name pattern)

_ PG (package name pattern)

_ SG (stogroup name pattern)

_ OS (object set name pattern)

_ SQ (dynamic SQL pattern)

_ RP (repository plan)



Probably the most powerful way of creating groups is by SQL pattern. With this option, you can include complex logic to select objects to process, that could include for example JOIN with user defined control tables to identify object that for example should never be processed.


In order to support the new object sets, new OBJECTSET syntax was added to Recover Plus for DB2, Copy Plus for DB2 and Log Master for DB2. This syntax allowed these products to read the new BMC Common DB2 repository and extract the list of objects to process. Of course, that made existing syntax like for example RMGROUP obsolete.


The new BMC Common DB2 repository included the following new tables:


_ object set (OBJSETS)

_ object set definition (OBJSET_DEF)

_ object set SQL (OBJSET_SQL)

_ group options (GRPOPTS)

_ product registration (PRODREG)

_ group authorizations (GROUPAUTH)


The repository is documented in detail in an Appendix in the supporting products User Guide.


These tables replaced the existing RECOVERY MANAGER tables used for group definition (In that first version, a utility was provided to migrate the content of the previous tables to the new ones).


Since them, several additional features or support have been added to the BMC Common DB2 repository. For example, in Version 10.1, RECOVERY MANAGER added OBJECTSET support for ARMBGEN, that allows creating Recovery groups using the OBJECTSET syntax. Also a new batch utility, ARMBSET, has been created to allow common DB2 commands or utilities, like STOP, to be executed at the OBJECTSET level.


But the main change occurred last June, when in version 11.1 a shared repository with DASD MANAGER PLUS was announced. From version 11.1, DASD MANAGER PLUS object sets are also stored in the BMC Common DB2 repository, enabling object sets to be shared across products. The BMC Common DB2 repository replaces the previous three tables used in the BMCASUnn database for Object sets definitions.


The repository is also documented in Chapter 2 of the DASD MANAGER PLUS for DB2 Reference, “DASD MANAGER PLUS database”. No data conversion is necessary when you upgrade from previous versions of DASD MANAGER PLUS to version 11.1.00 or later. The Installation System migrates the data for you.


This support adds also addition syntax and allows Actions defined in DASD MANAGER PLUS to be executed at the Object Set level.


I hope this article has been of interest, in future articles we will develop this topic and will include other BMC repositories.