WebSphere MQ Reports that Show CPU Time

This topics describes the Strobe Performance Profile reports that reveal CPU usage information about batch applications that access WebSphere MQ.

MQSeries CPU Usage Summary Report

The MQSeries CPU Usage Summary report (See the following figure) shows MQSeries activity caused by the application modules during a Strobe measurement session. During this measurement session, the section named ALPHA1 contained in module ABCRED spent 12.67% of the CPU usage recorded during the session making WebSphere MQ service calls to queues controlled by WebSphere MQ queue manager QMN1. When making WebSphere MQ service calls to queue manager QMN2, ALPHA1 accounted for 7.63% of CPU usage. Total session CPU usage for section ALPHA1 added up to 20.30%.

MQSeries CPU Usage Summary Report

image2021-2-8_12-7-14.png

MODULE NAME

The name of the module making the WebSphere MQ service call. If you specified the name of the common user module on the Strobe - MQ Series Data Collector Options panel, it will not be listed in this report.

SECTION NAME

The name of the control section making the WebSphere MQ service call.

CPU TIME PERCENT

The percentage of CPU time spent executing WebSphere MQ service calls. The percentage reflects CPU time used by programs executing for the measured application. There are two measures of CPU time:

  • SOLO shows WebSphere MQ activity without any concurrent I/O or CPU activity being performed under control of programs executed for the measured job step.
  • TOTAL shows WebSphere MQ activity with or without any such concurrent activity.

CPU Usage by Module by MQSeries Call

The CPU Usage by Module by MQSeries Call report (CPU Usage by Module by MQSeries Call Report) breaks out and shows how the WebSphere MQ activity for measured modules and their associated control sections and offsets is distributed over queue managers. For each queue manager, the storage location and service call appears. For each queue, the cumulative CPU usage for a service call is identified.

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

This report example covers module ABCRED. The first section shown is ALPHA1. Strobe reported that MQGET calls from location 00001A3E to queue QUEUE_RED_33 consumed 1.05% of CPU time.

From location 0000846A, Strobe found that MQGET calls accessed four different WebSphere MQ queues. The CPU consumption of these calls accounted for a total of 11.62% of the CPU time reported during the measurement session. Combined, these MQGET calls totaled 12.67% of the CPU time.

From module ABCRED and section ALPHA1, MQPUT1 calls were made from location 000022AA to two different queues under WebSphere MQ queue manager QNM2. These calls accounted for 7.63% of CPU time.

Important

If you set a threshold value in the WebSphere MQ call field of the  - Tailor Reports panel as explained in Measuring Applications that Call WebSphere MQ, the TOTAL value may not match the sum of the values reported for each call.  does not report detail lines for calls that show less CPU time than the threshold value you specified.

CPU Usage by Module by MQSeries Call Report

image2021-2-8_12-9-12.png

MODULE

The name of the module making the WebSphere MQ service call. If you specified the name of the common user module on the Strobe - MQ Series Data Collector Options panel, it will not be listed in this report.

Important

If a CICS transaction program or an IMS online transaction is terminating during the measurement session and  is unable to identify it, this column will list a pseudo module name beginning with a period (.) (for example, .MQSRIES). See Part 1, Strobe for CICS and Part 3, Strobe for IMS for more information about pseudo module names that can appear in this report.

SECTION

The name of the control section making the WebSphere MQ service call.

QUEUE MANAGER NAME

Name of the queue manager of the queue that was the target of the WebSphere MQ service calls.

REQUEST LOCATION

Storage location of individual service call in the control section.

MQSeries CALL

The type of service call made by the control section.

QUEUE NAME

Name of the WebSphere MQ queue holding the data that was the object of the service call. In most cases, this name is the name of the local queue. For a MQPUT1 call, however, this name is either the local queue name or the alias name (if an alias was used for the queue).

Note: The message UNABLE TO IDENTIFY QUEUE may appear in the queue name field if certain control blocks are not available to Strobe. WebSphere MQ control blocks may not be available at OPEN and CLOSE time. The message NO QUEUE APPLICABLE FOR THIS API may appear in the queue name field when Strobe is processing either internal APIs or MQCMIT and MQBACK APIs.

CPU TIME PERCENT

The percentage of CPU time spent executing WebSphere MQ service calls. The percentage reflects CPU time used by programs executing for the measured application. There are two measures of CPU time:

  • SOLO shows WebSphere MQ activity without any concurrent I/O activity being performed under control of programs executed for the measured job step.
  • TOTAL shows WebSphere MQ activity with or without any such concurrent I/O activity.

TOTAL CPU ACTIVITY

The total CPU time percentage attributed to the service calls to the queue manager.

CPU Usage by IMS Transaction Reporting

Strobe for WebSphere MQ also reports on 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, the location of the transaction and which queue manager was called by the transaction. CPU Usage by Module by MQSeries Call Report (Transaction Level) shows the format of the CPU Usage by Module by MQSeries Call report if you specify the MQTRAN parameter.

If you have identified an IMS transaction with high CPU time usage on the Summary of CPU Usage by Transaction report as described in the section MQSeries-IMS-Transaction-Summary-Reports, you can use this report to see the WebSphere MQ service calls being made by the transaction that used the most CPU time.

Strobe reports total CPU usage time on a queue manager, module and a transaction level as shown in the report field descriptions following CPU Usage by Module by MQSeries Call Report (Transaction Level).

As shown on the CPU Usage by Transaction Summary report shown in Summary of CPU Usage by Transaction Report, the transaction named IMSTRAN2 had a total CPU usage of 6.62 percent. You can see each WebSphere MQ service call that transaction IMSTRAN2 made during the measurement session.

CPU Usage by Module by MQSeries Call Report (Transaction Level)

image2021-2-8_12-11-27.png

Queue Manager Name Total

The total CPU usage time reported by Strobe for the queue manager called by the online IMS transaction module.

Module Name Total

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

Transaction Name Total

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

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*