Reading and Navigating Basic Reports (MQ)

This section provides report samples and detailed information for each of the basic reports.

HTML exception report

A standard HTML Exception Report compares the MQ_GET messages that occurred during playback (“actual”) to the MQ_GET messages recorded in the script (“expected”).

A baseline HTML Exception Report compares “actual” MQ_GET messages from two unattended playback data collections. The “actuals” from the baseline database are used as “expected” values for comparison.

An HTML Exception Report presents a summary of mismatches at the top of report followed by the “actual” and “expected” messages with highlighted differences. The messages in the summary are hyperlinked to the messages in the detail. Depending on the content of the script or the structure of the application you are testing, the report may also include the MQ_PUT message related to the reported MQ_GET messages.

View the report with a supported Web browser. Scroll up and down to view the entire report or click a message number in the summary to see the mismatch detail for that message.

The following figure shows a mismatch summary and HTML Exception Report Mismatch Detail shows the corresponding mismatch detail.

HTML Exception Report mismatch summary (Top of report)

Field definitions

The title specified on the REPORT statement or the default report title, Performance Test for WebSphere MQ - Exception Report, displays across the top of the window and in the title bar. In a baseline report, the following fields come from the database entered on the SET SORTED statement in the log file.

Run Date

The date and time that the unattended playback job was executed.

SYSID

The LPAR in which the playback job was executed.

Jobname

The playback job name.

Jobnumber

The playback job number.

Group Number

The number of the group in which the message was played back. Groups are numbered sequentially.

Script Number

The number of the script containing the reported message. Scripts are numbered sequentially within the group.

Script Name

The name of the script containing the reported message.

MessageSet Number

The connection number of the MessageSet (a group of related messages) containing the reported message. MessageSets are numbered sequentially within a script.

Message Number

The reported message’s number. Messages are numbered sequentially within a Message Set.

MQ Queue Manager and Queue

The MQ Queue Manager and Queue name associated with the reported message.

HTML Exception Report mismatch detail

Field definitions

Each group of “expected” and “actual” messages is preceded by the associated Group Number, Script Number, Script Name, Message Set Number, and Message Number. These are the same fields presented in the summary at the top of the report. See Field Definitions. Additionally, all of the fields displayed under the “expected” message also display under the “actual” message. Although the values they present may be different, the field definitions are the same.

Expected MQGET Message

The “expected” MQ_GET message. In a standard exception report, this comes from the script. In a baseline report, this comes from the baseline data collection. If the baseline was generated from an:

• Online playback, this is the MQ_GET message that resulted from the playback.
• ANALYZE playback (offline playback), this is the MQ_GET message from the script.

Mismatches are highlighted. Masked information displays in green text.

Message Type

The reported message’s type, for example, REQUEST, REPLY, DATAGRAM, or REPORT. This comes from the MQ message descriptor (MQMD).

Message Persistence

The reported message’s “persistence” setting. This comes from the MQMD.

ReplyToQueueManger

The name of the Queue Manager to receive the reported message’s reply. This comes from the MQMD. If the message is not supposed to reply, the MQMD does not contain a ReplyToQueue, and this field displays the name of the queue manager that the application was connected to during capture or playback.

ReplyToQueue

The name of the Queue to receive the reported message’s reply. This comes from the MQMD. Not all messages reply. This field is blank if the message’s MQMD does not possess this information.

MQ Message ID

The message ID from the reported message’s MQMD.

Correlation ID

The correlation ID from the reported message’s MQMD.

Actual MQGET Message

The “actual” MQ_GET message. In a standard exception report, this is the MQ_GET message that resulted from the playback. In a baseline report, this comes from the baseline data collection. If the baseline was generated from an:

• Online playback, this is the MQ_GET message that resulted from the playback.
• ANALYZE playback (offline playback), this is the MQ_GET message from the script.

Mismatches are highlighted. Masked information displays in green text.

Message Start Time

The date and time the reported message was received.

Actual MQPUT Message

The MQPUT message related to the preceding MQGET message. This section appears only if there is a correlating MQPUT message.

Script Timing Summary

A Script Timing Summary Report shows the amount of time it took for each script to play back and provides additional timing statistics for the playback job.

Generate an HTML or TEXT version of the report. View the HTML version with a supported web browser.

The following figure shows an HTML Script Timing Summary. Field definitions follow the illustration.

HTML Script Timing Summary Report

Field definitions

The title you specified on the REPORT statement or the default report title, Performance Test for WebSphere MQ - Script Timing Summary Report, displays across the top of the report. In an HTML version, the report title also appears in the title bar of the browser window.

Run Date

The date and time that the playback job was executed. This field appears only on the HTML version of the report.

SYSID

The LPAR in which the playback job was executed. This field appears only on the HTML version of the report.

Jobname

The playback job name. This field appears only on the HTML version of the report.

Jobnumber

The playback job number. This field appears only on the HTML version of the report.

MQGroup Number

The number of the group in which the reported script was played back. Groups are numbered sequentially.

Script Name

The name of the script.

Number

The number of the script being reported. Scripts are numbered sequentially within the group.

Start Time

The date and time the given script began playing back.

Finish Time

The date and time playback completed for the given script.

Duration

The amount of time it took for the given script to play back.

MQGroup Total

A row of statistics for each MQGroup played back.

Number

The total number of scripts within the group.

Minimum Duration

The shortest playback duration in the group.

Maximum Duration

The longest playback duration in the group.

Average Duration

The average of all playback durations in the group.

Report Total

A row of statistics for the entire playback job.

Number

The total number of scripts played back.

Minimum Duration

The shortest playback duration in the job.

Maximum Duration

The longest playback duration in the job.

Average Duration

The average of all playback durations in the job.

Response Time Summary

A Response Time Summary Report shows the amount of time it took each group of related messages to occur. For example, the amount of time it took to receive the MQ_GET from the time the correlating MQ_PUT was sent.

Generate an HTML or TEXT version of the report. View the HTML version with a supported Web browser.

The following figure shows an HTML Response Time Summary. Field definitions follow the illustration.

HTML Response Time Summary report

Field definitions

The title you specified on the REPORT statement or the default report title, Performance Test for WebSphere MQ - Response Time Summary Report, displays across the top of the report. In an HTML version, the report title also appears in the title bar of the browser window.

Run Date

The date and time that the playback job was executed. This field appears only on the HTML version of the report.

SYSID

The LPAR in which the playback job was executed. This field appears only on the HTML version of the report.

Jobname

The playback job name. This field appears only on the HTML version of the report.

Jobnumber

The playback job number. This field appears only on the HTML version of the report.

MQGroup Number

The number of the group in which the reported script was played back. Groups are numbered sequentially.

Script Name

The name of the script.

Number

The number of the message being reported. Messages are numbered sequentially within the connection.

ID

The ID Performance Test for WebSphere MQ assigns the message set, group of related messages, during playback.

Start Time

The date and time the given message set began playing back.

Finish Time

The date and time playback of the message set is completed.

Duration

The amount of time it took for the given message set to play back.

Total

A row of statistics for the given script.

Number

The total number of message sets within the script.

Minimum Duration

The shortest response duration within the script.

Maximum Duration

The longest response duration within the script.

Average Duration

The average of all response durations for the given script.

MQGroup Total

A row of statistics for each MQGroup played back.

Number

The total number of message sets within the group.

Minimum Duration

The shortest response duration in the group.

Maximum Duration

The longest response duration in the group.

Average Duration

The average of all response durations in the group.

Report Total

A row of statistics for the entire playback job.

Number

The total number of message sets played back.

Minimum Duration

The shortest response duration in the job.

Maximum Duration

The longest response duration in the job.

Average Duration

The average of all response durations in the job.