APM Team Center

Beginning with release 10.2, certain mainframe components can be displayed in the APM Team Center (ATC) user interface.
ccapm102
Beginning with release 10.2, certain mainframe components can be displayed in the APM Team Center (ATC) user interface.
This section provides information specific to mainframe components only. For general documentation about APM Team Center, see the APM Team Center section in the APM documentation.
Supported Components and Relationships
The APM Team Center user interface supports three types of mainframe components:
  • CICS regions
  • IMS subsystems
  • DB2 subsystems
Any of these components that are monitored by Cross-Enterprise APM and that are part of instrumented transactions will be displayed in APM Team Center. For details on how to instrument them, see the How to Trace Cross-Process Transactions.
All supported components have a default selection of metrics and alerts relevant to their status attached out of the box.
Apart from the common basic attributes that are assigned to all ATC components mainframe components have some additional attributes or attributes with specific meaning. They are listed below.
The following table shows the basic attributes specific to CICS region components:
Attribute
Meaning
jobName
CICS jobname
applid
The CICS-specific VTAM application ID
The following table shows the basic attributes specific to IMS subsystem components:
Attribute
Meaning
applicationName
IMS subsystem name
The following table shows the basic attributes specific to DB2 subsystem components:
Attribute
Meaning
SSID
DB2 subsystem id
The set of relationships supported for mainframe components is based on the available Cross-Process instrumentation capabilities and includes:
  • Call to a CICS region initiated through a CICS Transaction Gateway server.
  • Call to a CICS region through its Web Service connection.
  • Call to a CICS region or IMS subsystem initiated through WebSphere MQ.
  • DB2 operations initiated by a CICS transaction.
Known Limitations
Relationships Between Mainframe Components
There are limitations to how relationships involving mainframe components are shown in specific scenarios.
For client calls to CICS that go through a CICS Transaction Gateway that is itself instrumented and represented in APM Team Center, there will be one relationship between the client component and the CICS component and another, separate relationship between the client and the CTG component. No relationship between the CTG component and the CICS component will be shown.
For transactions involving calls to multiple CICS or IMS components, the relationships will not be always shown properly. In these cases, the relationships will be based on timing information that is not always accurate. As a consequence, the overall structure might include relationships that do not exist directly.
Differential Controls
Due to current Cross-Enterprise APM agent limitations, differential control definitions based on standard Cross-Enterprise APM metrics do not always behave correctly.
In order to support differential control alerts attached to mainframe ATC nodes, the mainframe differential controls shipped with the product use a separate set of metrics generated specifically for this purpose. These metrics reside under the
Differential Control
metric folder and should not be used for any other purpose because they might be removed in a future release.