MQSeries IMS Transaction Summary Reports


Strobe for WebSphere generates two reports that provide measurement information about online IMS transactions. One report contains a summary of CPU usage by IMS transaction and the other report contains a summary of wait time by IMS transaction.

Summary of CPU Usage for IMS Transactions

The following figure shows the MQSeries Summary of CPU Usage by Transaction report. For each online IMS transaction that occurs during the measurement session. Strobe provides both solo and total percentages for CPU usage. You can use this report information to augment the report data provided by Strobe for IMS.

A transaction named IMSTRAN2 caused a high 6.62 percent usage of the CPU time during the Strobe measurement session. Setting the MQTRAN parameter as explained in IMS Transaction Level Reporting causes Strobe to obtain individual IMS transaction report data. Then by referring to the section CPU Usage by Module by MQSeries Call, you can identify what calls to WebSphere MQ are causing the most of the IMSTRAN2 transaction CPU usage.

Summary of CPU Usage by Transaction Report

image2021-2-8_13-38-19.png

TRANSACTION NAME

The name of the IMS transaction causing CPU usage resulting from making a WebSphere MQ service call.

For a description of the other fields shown on the Summary of CPU Time report, see WebSphere-MQ-Reports-that-Show-CPU-Time.

Summary of Wait Time for IMS Transactions

The following figure shows the Summary of Wait Time by Transaction. For each online IMS transaction that occurs during the measurement session. Strobe provides both solo and total percentages for wait time. You can use this report information to augment the report data provided by Strobe for IMS.

A transaction named IMSTRAN3 caused 2.31 percent of the wait time during the Strobe measurement session. Setting the MQTRAN parameter as explained in IMS Transaction Level Reporting causes Strobe to obtain individual IMS transaction report data. Then by referring to the section Wait by Module by MQSeries Call Report, you can identify what calls to WebSphere MQ are causing the most of the IMSTRAN3 transaction wait time.

Summary of Wait Time by Transaction Report

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

TRANSACTION NAME

The name of the IMS transaction causing wait time resulting from making the WebSphere MQ service call.

For a description of the other fields shown on the Summary of Wait Time By Transaction reports, see WebSphere MQ Reports that Show Wait Time.

 

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

BMC AMI Strobe 21.01