Introduction to metrics found in MQ Accounting records and ways value can be derived from this typically large data source by viewing the data at various levels of detail including connection type and caller details.


More MQ Accounting Videos

  1. Overview of MQ Accounting Data
  2. Viewing Accounting Data by Queue Level
  3. Viewing Accounting Data by Connection Type
  4. Selected Accounting Data Metrics – Part 1
  5. Selected Accounting Data Metrics – Part 2
  6. Sample MQ Statistics and Accounting Dashboards

Video Transcript

So now let’s go ahead and transition and talk about learning from the MQ Accounting data. So the SMF type 116 records contain detailed task-level data, and most of the accounting data is only generated when Class 3 is specified on the start trace accounting command. The default Class 1 data provides only a very limited set of metrics.

So gaining value from really any large data source is typically achieved through focusing the analysis on a subset of the data. So this is a list of many levels at which the accounting data can be viewed. One common line of analysis is activity for specific queues, including depth of messages on a queue or time that messages spend on a queue. And then another common focus for MQ accounting data, as is also the case with Db2, is by connection type, differentiating characteristics of the activity across various callers of MQ. And the remaining items there under the second column indicate more ways that the accounting data can be subdivided, and typically those will follow an initial focus by connection type.

So the availability of those additional levels of detail differ by connection type. So if the MQ work coming from batch or TSO, then in the connection name field, you get the address space name. The channel initial work can be viewed by the CHIN address space name as well as the channel name and IP address. For CICS, in addition to region name, you’re likely going to want to view the MQ work by transaction ID. Command server work can be viewed by queue manager. And the workload coming from IMS can be viewed by IMS subsystem name and also by program specification block, which often provides an application-oriented view of that work. And then for reference, here are examples of the types of metrics that are present in the accounting data.

You May Also Be Interested In:


What's New with IntelliMagic Vision for z/OS? 2024.2

February 26, 2024 | This month we've introduced changes to the presentation of Db2, CICS, and MQ variables from rates to counts, updates to Key Processor Configuration, and the inclusion of new report sets for CICS Transaction Event Counts.

Read more

Viewing Connections Between CICS Regions, Db2 Data Sharing Groups, and MQ Queue Managers

This blog emphasizes the importance of understanding connections in mainframe management, specifically focusing on CICS, Db2, and MQ.

Read more

What's New with IntelliMagic Vision for z/OS? 2024.1

January 29, 2024 | This month we've introduced updates to the Subsystem Topology Viewer, new Long-term MSU/MIPS Reporting, updates to ZPARM settings and Average Line Configurations, as well as updates to TCP/IP Communications reports.

Read more

Explore MQ Performance Management and Monitoring

Book a Demo or Connect With an Expert

Discuss your technical or sales-related questions with our mainframe experts today