Db2 subsystem discovery

To avoid unnecessarily populating a potentially high volume of instances and impacting CCMDB performance, by default, Db2 Database, Db2 Tablespace and Db2 Bufferpools instances are not populated.

Whenever a Db2 has a configuration change, its catalog tables are updated. For example, a change to a Db2 Table column definition updates the SYSCOLUMNS catalog table. For each configuration change, an altered timestamp is updated in the catalog. The DLA discovers the maximum altered timestamp for the following catalog tables: SYSDATABASE, SYSTABLESPACE, SYSTABLES, SYSINDEXES and SYSCOLUMNS. These timestamps are saved as attributes. If a subsequent discovery for the subsystem discovers a different maximum altered timestamp, the CCMDB is able to highlight that the Db2 has had a configuration change. This is a highly efficient way to detect changes without the overhead of loading high volumes of low-level resources.

Db2 Subsystems can be configured to have their own data resources, or to share data resources with other Db2 Subsystems by using a Db2 Data Sharing Group. The z/OS® DLA automatically discovers both types of Db2 environments.

The associated components that comprise the Db2 Subsystem are associated to the Db2 Subsystem. The address spaces for the MSTR, DIST, IRLM, DIST and SPAS components contain a federates relationship to the Db2 Subsystem.

The following diagrams show the classes and relationships that are populated in the Db2 books. The boxes that are clear are not populated.

See the Appendix C. z/OS DLA data model class types represented in CDM section for details on what attributes and relationships are discovered for these classes.