Enqueue and Dequeue metrics missing for specific IBM MQ Queue Manager
search cancel

Enqueue and Dequeue metrics missing for specific IBM MQ Queue Manager

book

Article ID: 448819

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope) DX Application Performance Management

Issue/Introduction

In some environments using the IBM MQ Infrastructure Agent, you may find that specific activity metrics like Enqueue Count and Dequeue Count are missing for one Queue Manager while other metrics (Queue Depth, Open Input/Output Count) continue to report correctly. This occurs even when multiple Queue Managers on the same host share identical configurations.

Symptoms

  • Queue Manager is discovered and connected correctly.
  • Connectivity and depth metrics are visible in the investigator.
  • Enqueue Count and Dequeue Count metrics are missing or not created.
  • Infrastructure Agent logs may show error code 2101 during PCF command execution.
  • Difference in DISPLAY PUBSUB ALL status (e.g., status shows ERROR for the affected manager).

Environment

  • IBM MQ Infrastructure Agent 24.7.1.4 and higher
  • IBM MQ 9.3.x
  • Linux (Red Hat Enterprise Linux 8.x)

Cause

This issue is caused by the corruption of an internal IBM MQ object. When an object becomes corrupted, the Queue Manager cannot process the PCF commands (such as MQCMD_RESET_Q_STATS or MQCMD_INQUIRE_Q_STATUS) required by the agent to collect activity metrics.

Resolution

  1. Review the IBM MQ Queue Manager error logs (e.g., AMQERR01.LOG) and .FDC files for indications of corrupted objects or error code 2101.
  2. Coordinate with the IBM MQ Administrative team to identify the corrupted object within the problematic Queue Manager.
  3. Restore or recreate the affected MQ object.
  4. Restart the APM Infrastructure Agent (APMIA) service to initiate a new polling cycle.
  5. Verify that Enqueue and Dequeue metrics are now populating in the Metric Browser.

Additional Information

If the metrics remain missing after restoring the objects, ensure that the agent has the necessary permissions. You can verify and refresh security using these commands:

⚠️ IMPORTANT: Always test command updates first in a non-production environment. Take a backup before implementing in production.

/opt/mqm/bin/setmqaut -m #### -n '**' -t queue -p +allrunmqsc ####REFRESH SECURITYEND

For further assistance, see .