Detecting and correcting high queue depth

IBM® Service Management Unite can detect and restore service for a queue with high depth.

The consolidated event viewer displays monitoring and automation exception events, filtered by severity and customized for your area of support. In this scenario, the top unacknowledged event is a warning for a group resource that is owned by the MQ queue manager Q7G4. The user right-clicks on the event and selects View MQ Queue Manager Details for Q7G4.

The MQ Queue Manager Details page displays key performance and status metrics for resources that are owned by queue manager Q7G4. The performance graphs and tables show that queue EAP.S2.APP.IN.Q2 has a high percent full value compared to its defined high depth threshold.

The user selects the bar on the Queues with High Depth graph that represents EAP.S2.APP.IN.Q2 and selects Isolate Problem. In the Problem Isolation - Queue Has High Depth page, problems and solutions are listed under the Suggested Actions view. One of the recommended solutions is to increase the maximum depth that is defined for the queue, which is currently defined as 50.

From the Queue Manager Events table, the user selects the Execute Command action to open the Execute Command page. In the Command field, the user enters the command <Q7G4 ALTER QLOCAL(EAP.S2.APP.IN.Q2) MAXDEPTH(150) and clicks Go. The command results returned on the page indicate that the queue depth was successfully changed.

The user contacts the owner of the application with details on the problem.