Custom rules for CICS, IMS and MQ monitoring

Dynatrace automatically traces CICS and IMS transactions when they are called by already-monitored services. Transactions that start on the mainframe or are called by unmonitored services require specific rules to be monitored. There are two types of such rules:

  • Global level rules.
  • Process group level rules. These rules override global rules on a process group level

To define rules for monitoring transactions of unmonitored services

  1. Go to Settings > Server-side service monitoring > Deep monitoring.
  2. Expand the CICS, IMS, and MQ monitoring section and define the required rule. Find the details in the appropriate subsections below.

Transaction monitoring

You can monitor CICS and IMS transactions that start from a 3270 terminal by adding the transaction IDs to the monitoring filter.

  • Dynatrace automatically traces CICS and IMS transactions that are called from already-monitored services. You don't need to create rules for them.
  • Adding a transaction ID to the monitoring filter will start a new PurePath and it won't be linked to a previous subpath, regardless of how the transaction was initiated.
  1. Click Add CICS start transaction ID filter or Add IMS start transaction ID filter.
  2. Enter the transaction ID and click Add.

MQ monitoring

To incorporate your z/OS queues into end-to-end service tracing, Dynatrace needs to know some details about your queues.

Alias, remote, and cluster queues

You can define alias, remote, and cluster queues via the queue manager endpoints of the IBM MQ tracing API.

Alternatively, you can use the IBM MQ extension to automatically retrieve the queue topology from your environment:

  1. Enable Retrieve queue topology for improved transaction tracing in the IBM MQ extension.
  2. Provide the API endpoint and API token key.
  3. Save the changes.

IMS MQ Bridge queues

You can define the queueName and queueManagerName for IMS MQ Bridge queues via the IBM IMS entry queue endpoints of the IBM MQ tracing API.

Capture only specific queues

By default, Dynatrace captures all CICS MQ and IMS MQ queues. You can define rules to capture only specific queues. For IMS these rules apply to application regions.

When you add a queue to the include list all other queues are ignored.

  1. Click Add CICS MQ queue ID include filter or Add IMS MQ queue ID include filter.
  2. Enter the queue ID and click Add.

When you add a queue to the exclude list remaining queues are still monitored.

  1. Click Add CICS MQ queue ID exclude filter or Add IMS MQ queue ID exclude filter.
  2. Enter the queue ID and click Add.

IMS MQ Bridge transaction monitoring

By default, Dynatrace captures all the transactions that are submitted via IMS MQ Bridge. You can define rules to capture only specific transactions.

When you add a transaction ID to the include list, all the remaining transactions are ignored.

When you add a transaction ID to the exclude list remaining transactions are still monitored.

  1. Click Add IMS MQ transaction ID include filter or Add IMS MQ transaction ID exclude filter.
  2. Enter the transaction ID and click Add.

Node limit

The node limit is the maximum number of nodes in the PurePath, which will be captured for a single CICS or IMS program call. We recommend the limit of 500, which is the default. The value of 0 means unlimited number of nodes.

Caution

Increasing the limit above 500 might cause a significant CPU overhead on z/OS.