CICSPLEX discovery library books contain information about CICSPlex® SM
resources associated with a specific CICSplex. These discovery library
books have names starting CICSTS410CICSPLEX.cicsplex_name,
where cicsplex_name is the name of a CICSplex as
supplied in the CPLEXDEF attribute CPLEXDEF_CICSPLEX.
The DLA populates all attributes discovered about the
following classes:
- ManagementSoftwareSystem
- The product that discovered the resources in the discovery library
book. It includes these attributes:
- ProductName: IBM® CICS® TS Discovery Library Adapter
- ProductVersion: The current version of CICS TS; for example, 410
- Organization
- A global name to preserve uniqueness in the CCMDB. This name is
needed because you might have multiple z/OS® systems
with the same identifiers; for example, a copy of a production z/OS running
on different hardware for testing purposes. You set the global name
from the ORGNAME input parameter at DLA run time or from the default
value when the discovery library book is loaded into the CCMDB.
- CICSplex
- Information about CICSplexes.
- CICSRegionGroup
- Information about CICS region groups.
- CICSManagingAddressSpace
- Information about CICSPlex SM CMASs.
- CICSWUIEndPoint
- Information about CICSPlex SM Web User Interface
(WUI) servers. This class includes the WUI URL as an attribute. You
can use this URL to launch the WUI. The CICSWUIEndPoint instances
in a given CICSPLEX discovery library book might be for WUI servers
that are running in different CICSplexes. Each CICSPLEX discovery
library book must contain a CICSWUIEndPoint instance with a relationship
type of Accesses for each WUI server associated
with the CMAS.
- Application
- Data for business applications that you have defined using BAS
logical scopes. You obtain the application names from logical scope
names; that is, from the RESDESC_LSCOPE attribute specified in the
BAS resource description (RESDESC) resource table.
The following classes exist as stub instances
in the discovery library book. The only attributes produced are those
attributes needed to satisfy the naming rules for relationships to
these classes.
- CICSRegion
- CICS region resources
- CICSFile
- File resources
- CICSLIBRARY
- LIBRARY resources
- CICSDocumentTemplate
- Document template resources
- CICSLSRPool
- VSAM LSR pool resources
- CICSTDQueue
- Transient data queue resources
- CICSTransaction
- Transaction resources
- CICSProgram
- Program resources
- CICSProfile
- Transaction profile resources
- CICSDb2Entry
- DB2® entry resources
- CICSDb2EntryTransaction
- DB2 entry associated transaction resources
The relationships in
Table 1 apply to a CICSplex.
The Manages relationship between CICSManagingAddressSpace (CMAS) and
CICSplex identifies which CMASs participate in managing the CICSplex.
The Controls relationship identifies the maintenance point CMAS. A
maintenance point CMAS is responsible for notifying the other CMASs
about changes of topology in the CICSplex. Each CICSplex has one maintenance
point CMAS but a CMAS can act as a maintenance point for several CICSplexes.
Table 1. Relationships for CICSplex| Relationship type |
Source |
Target |
| Accesses |
CICSWUIEndPoint |
CICSplex |
| Controls |
CICSManagingAddressSpace |
CICSplex |
| Federates |
CICSplex |
Application |
| Federates |
CICSplex |
CICSRegionGroup |
| Federates |
CICSplex |
CICSRegion |
| Manages |
CICSManagingAddressSpace |
CICSplex |
| Owns |
Organization |
CICSplex |
The relationships in
Table 2 apply to CICS
region groups. A CICS region group can include multiple CICS regions
and other CICS region groups.
Table 2. Relationships for CICS region groups | Relationship type |
Source |
Target |
| Federates |
CICSplex |
CICSRegionGroup |
| Federates |
CICSRegionGroup |
CICSRegion |
| Federates |
CICSRegionGroup |
CICSRegionGroup |
| Owns |
Organization |
CICSRegionGroup |
The relationships in
Table 3 apply to the technology
providing the DLA data to the CICSManagingAddressSpace, CICSWUIEndPoint
classes, and CICSRegion classes.
Table 3. Relationships for CICSManagingAddressSpace, CICSWUIEndPoint
and CICSRegion classes| Relationship type |
Source |
Target |
| Contains |
MSSInstance |
CICSManagingAddressSpace |
| Contains |
MSSInstance |
CICSWUIEndPoint |
| Relates |
MSSObjectLink |
CICSRegion |
The relationships in
Table 4 associate
an application with a CICSplex and with installed resource instances
in CICS regions.
Table 4. Relationships
that associate an application with a CICSplex and with installed resources| Relationship type |
Source |
Target |
| Contains |
CICSRegion |
CICSFile |
| Contains |
CICSRegion |
CICSDb2Entry |
| Contains |
CICSRegion |
CICSDb2EntryTransaction |
| Contains |
CICSRegion |
CICSProfile |
| Contains |
CICSRegion |
CICSDocumentTemplate |
| Contains |
CICSRegion |
CICSLibrary |
| Contains |
CICSRegion |
CICSLSRPool |
| Contains |
CICSRegion |
CICSProgram |
| Contains |
CICSRegion |
CICSTDQueue |
| Contains |
CICSRegion |
CICSTransaction |
| Federates |
CICSplex |
Application |
| Uses |
Application |
CICSDb2Entry |
| Uses |
Application |
CICSDb2EntryTransaction |
| Uses |
Application |
CICSDocumentTemplate |
| Uses |
Application |
CICSFile |
| Uses |
Application |
CICSLibrary |
| Uses |
Application |
CICSLSRPool |
| Uses |
Application |
CICSProfile |
| Uses |
Application |
CICSProgram |
| Uses |
Application |
CICSTDQueue |
| Uses |
Application |
CICSTransaction |