MQSeries Total CPU Activity by Queue Report

For each WebSphere MQ queue manager, the MQSeries Total CPU Activity by Queue report (see the following figure) provides a summary of the 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 queues. The first queue accounted for a total of 15.12% of CPU activity and the second queue’s activity correlated to 14.34% of the CPU time attributed to the queue. The remaining report fields provide different types of information about the messages received on each queue and are described in the following section. These fields just report information about messages that were observed by Strobe. A message not observed could have one of the noted characteristics, but was not sampled by Strobe.

MQSeries Total CPU Activity by Queue Report

image2021-2-8_13-21-34.png

COUNT

The number of times the WebSphere MQ call was made. Counts are reported for the following types of calls:

  • MQOPEN
  • MQCLOSE
  • MQPUT
  • MQPUT1
  • MQGET
  • MQINQ
  • MQSET.

COA (Confirmed on Arrival)

Whether a message that was written specified that a confirmation of arrival (COA) is generated when the message has been put on its final destination queue.

COD (Confirmed on Delivery)

Whether a message that was written specified that a confirmation of a delivery (COD) is generated when the message has been retrieved from its final destination queue.

BROWSE

On a MQGET call, the message was copied, but not removed, from the queue.

DATA CONV

One or more MQGET service calls specified that the application data in the message is converted to conform to the values in the message descriptor.

WAIT

An MQGET call was issued with a specification of a maximum time that WebSphere MQ is to wait for the specified message to arrive on the queue.

CORL ID

One or more service calls specified a correlation ID.

SYNC POINT

One or more messages were read or written with a synchronization point specified.

CPU Activity by Queue by Module

The CPU Activity by Queue by Module report (see the following figure) shows the activity caused by application modules that access WebSphere MQ and provides a list of characteristics of the messages associated with the application activity.

MQSeries Messages CPU Activity by Queue Module

image2021-2-8_13-23-34.png

PRIORITY RANGE

This field identifies the range of priorities for the WebSphere MQ messages observed by Strobe for WebSphere MQ during measurement.

SMALLEST MESSAGE

This field indicates the size of the smallest message sent to or received by the module section. If the value is 1- 999,999 bytes, the number of bytes is listed without any notation. If the value is one megabyte or more, M appears after the number. In the case of MQPUT and MQPUT1 calls, this value is the size of the message specified in the service call. For MQGET calls, this value indicates the buffer length specified in the service call.

LARGEST MESSAGE

This field indicates the size of the largest message sent to or received by the module section. If the value is 1- 999,999 bytes, the number of bytes is listed without any notation. If the value is one megabyte or more, M appears after the number. In the case of MQPUT and MQPUT1 calls, this value is the size of the message specified in the service call. For MQGET calls, this value indicates the buffer length specified in the service call.

AVER SIZE

This field indicates the average size of the messages sent to or received by the module section.

 

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