WebSphere MQ Reports that Show Wait Time

The Strobe for WebSphere MQ Performance Profile also includes a set of reports that identify the wait time that application modules spent when making service calls to WebSphere MQ. Four reports are produced for batch and CICS jobs that are similar in format to the reports produced for CPU usage.

MQSeries Wait Summary

The MQSeries Wait Summary report (MQSeries Wait Summary Report) shows a summary of the wait time experienced by application modules due to making WebSphere MQ service calls. During this measurement session, service calls to queue manager QMN1 from section GAMMA4 of module ABCGREEN accounted for 15.48% of the run time spent in wait. Service calls to queue manager QMN2 accounted for 4.48% of the run time spent in wait.

RUN TIME PERCENT

The percentage of time during the measurement session that the address space was in the wait state. There are two measures of run time:

• PAGE shows wait time that results from retrieving a page from the page data set. A high value in this column indicates that there is not enough physical memory assigned to the address space. If you noticed a high paging rate on the Measurement Session Data report, the Wait Time by Module report enables you to see which module was experiencing delay because of paging.
• TOTAL measures all causes of wait time, including page retrieval, programmed I/O operations, and timer requests.

For a description of the other fields in this time report’s fields, see MQSeries CPU Usage Summary Report.

MQSeries Wait Summary Report

Wait by Module by MQSeries Call Report

The Wait by Module by MQSeries Call report (Wait by Module by MQSeries Call Report) breaks out and shows the percentage of run time spent in wait caused by WebSphere MQ activity for measured modules and their sections and how it is distributed over queue managers. For each queue manager, the storage location and service call is displayed. The cumulative percentage of run time spent in wait by a service call is provided for each queue manager.

If you set the MQTRAN report parameter, this report will contain data showing online IMS transaction level activity. See IMS Transaction Level Wait Time Reporting for an example of the report format when the MQTRAN parameter is set.

 In this report example, the WebSphere MQ calls issued from sections GAMMA4 and MEGA2 of module ABCGREEN are identified. The MQGET calls from location 00001A3E in section GAMMA4 to the queues managed by QMN1 took 11.13% of the run time spent in wait. The MQPUT calls from location 00002468 consumed 4.35% of the run time spent in wait. The MQGET calls to the queue manager QMN2 from section GAMMA4 took 4.48% of the run time spent in wait. A total of 19.96% of run time spent was reported for section GAMMA4.

For section MEGA2, the total percentage of run time spent in wait for MQPUT calls made from location 0000111E to the QMN1-managed queues shows the same percentage as the WAIT SUMMARY report, 0.24%. The sum of the run time spent in wait for these two sections matches the total shown in the last report: 20.20% of the measurement run time was spent in wait.

For a description of this report’s fields, see CPU Usage by Module by MQSeries Call.

Wait by Module by MQSeries Call Report

IMS Transaction Level Wait Time Reporting

Strobe for WebSphere MQ also reports wait time for IMS transactions that execute in an online environment. As explained in IMS Transaction Level Reporting, you can set the MQTRAN parameter to enable Strobe to report measurement information for IMS transactions. This information includes the transaction name, the module(s) from which the WebSphere MQ call was made, and the location of the transaction. Wait by Module by MQSeries Call Report (Transaction Level)shows the format of the Wait by Module by MQSeries Call report if you specify the MQTRAN parameter.

If you have identified an online IMS transaction with high wait time on the Summary of Wait Time by Transaction report as described in the section MQSeries-IMS-Transaction-Summary-Reports, you can use this report to find the WebSphere MQ service calls causing the most wait time. Strobe reported that transaction IMSTRANS3 took 2.31 percent of the wait time. By looking up IMSTRAN3 here, you can see the WebSphere MQ service calls that caused the wait time.

Wait by Module by MQSeries Call Report (Transaction Level)

Queue Manager Name Total

The total wait time reported by Strobe for the online IMS transaction resulting from making calls the queue manager

Module Name Total

The total wait time reported by Strobe for the online IMS transaction module.

Transaction Name Total

The total wait time reported by Strobe for the online IMS transaction.

MQSeries Total Wait by Queue Report

The Total Wait by Queue report (MQSeries Total Wait by Queue Report) provides a summary of messages received on a WebSphere MQ queue and includes information about the characteristics of the messages. In this measurement session, the queue manager QMN1 was handling two WebSphere MQ queues. The first queue accounted for a total of 7.00% of run time spent in wait time and the second queue’s activity correlated to 14.34% of the run time spent in wait attributed for the measurement session.

See MQSeries-Total-CPU-Activity-by-Queue-Report for a description of this report’s fields.

MQSeries Total Wait by Queue Report

MQSeries Messages Wait by Queue by Module Report

The Messages Wait by Queue by Module report (see the following figure) shows the wait time experienced by application modules that make service calls to a WebSphere MQ queue and provides a list of characteristics of the messages associated with the application activity.

See CPU Activity by Queue by Module for a description of the report fields.

MQSeries Messages Wait by Queue By Module