Created , Updated

The predefined MQ monitors all provide a message that details the problem that is occurring in the MQ component. Based on the MQ metric that triggered the monitor, we give a MQ administrator recommendation to help solve the problem.

Example MQ Datadog Monitor

Example configuration of a MQ Checkpoints Monitor

Status and History view of monitor

Monitors

Insufficient storage events is too high on QMGR

Relevant Metric

mainstorconcept.zos.mq.storage.insufficient_storage.events

Message

When MQ contracts storage, it indicates that the queue manager lacks sufficient storage. The queue manager compresses storage pools to reclaim unused capacity. Insufficient storage events occur when there is not enough storage available to satisfy a request after this compression occurred.

Recommendation

To resolve critical virtual storage shortages, either reduce the size of 31 bit buffer pools or move to 64 bit buffer pools.

MQ active dataset reads is too high on QMGR

Relevant Metric

mainstorconcept.zos.mq.log.active_dataset.reads

Message

If MQ data is not in memory it will be read from a log data set. MQ should not read data from the active log data sets.

Recommendation

An increase in transaction workload, transactions with higher latency or an increase in rolled back long-running transactions may cause data to be read from active log datasets.

MQ reading log data from archive log datasets on QMGR

Relevant Metric

mainstorconcept.zos.mq.log.archive_dataset.read

Message

MQ should not read log data from archive dataset.

Recommendation

Examine anomalies in MQ client transactions, e.g. high load transactions and higher than average latency and rolled back transactions. Additionally, increasing the number of active log data sets or increasing the size of active log data sets may be required.

Number of MQ Tasks Suspensions are too high on QMGR

Relevant Metric

mainstorconcept.zos.mq.log.waits

Message

MQ requests are being suspended while the in-storage buffer is being written to the active log. This indicates potential issues writing to the active log.

Recommendation

Increasing the size of output buffer storage for active and archive log data sets (i.e. CSQ6LOGP OUTBUFF parameter) may be too small.

Number of storage contractions is too high on QMGR

Relevant Metric

mainstorconcept.zos.mq.storage.contractions

Message

MQ detected a problem and recovery actions were taken and indicates a severe problem within the queue manager. When MQ contracts storage, it indicates that the queue manager lacks sufficient storage and had to compress storage pools to reclaim unused capacity.

Recommendation

To resolve virtual storage shortages, either reduce the size of 31 bit buffer pools or move to 64 bit buffer pools.

Value of checkpoints is too high on QMGR

Relevant Metric

mainstorconcept.zos.mq.log.checkpoints

Message

Busy MQ queue managers will have about 10 checkpoints per hour. Higher rate of checkpoints may indicate a queue manager setup problem.

Recommendation

Consider increasing the number of log records written by MQ between the start of one checkpoint and the next (i.e. CSQ6SYSP LOGLOAD parameter). Alternatively, increasing the size of active log datasets will reduce the checkpoint rate (i.e. CSQ6SYSP OUTBUFF parameter).