IMS subsystem discovery
- IMS Subsystem details and relationships
- IMS Sysplex Group details and relationships
- Program details and relationships
- Transaction details and relationships
- Database details and relationships
- IMS Connect details and relationships
- Reports:
- Programs
- Transactions
- Databases
To avoid a potentially high volume of instances being populated unnecessarily and impacting CCMDB performance, by default, IMS transactions, programs and databases are not populated.
Unlike Db2®, IMS does not have timestamps that can be discovered to detect configuration changes. However the DLA does have highly efficient discovery code for transactions, programs and databases via memory control blocks. The DLA internally performs the discovery and calculates a checksum value for each resource type, and these checksums are saved as attributes. If a subsequent discovery for the subsystem discovers a different checksum, the CCMDB is able to highlight that the IMS 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.
The following diagram shows the classes and relationships that are populated in the IMS books. The boxes that are clear are not populated.
See Appendix C. z/OS DLA data model class types represented in CDM for details on what attributes and relationships are discovered for these classes.