Viewing MQ Accounting Data by Connection Type

Examples of how MQ Accounting data is commonly viewed by the connection type of the MQ caller, and additional levels of detail that are available by connection type.

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 kind of start from some high-level views that start from a connection type. So here’s CPU, all the CPU in the environment, and the three primary drivers of MQ CPU here are channel initiators and CICS, and IMS. As we mentioned earlier, the CICS work can be viewed by transaction ID. And so that enables a view of MQ CPU that’s generated by each transaction.

If we look at this particular transaction over this time interval, we see that the CPU is decreasing, and many times when you observe some data that you’re going to want to kind of compare it to some other interval. And so we do that for a couple of days earlier in the week here. And we see that it’s in both intervals, there was a steady decrease of CPU from the beginning to the end of the interval.

So let’s look at CPU by the batch and TSO. There’s not much CPU there, but as we said earlier, when you look at that by connection name, you see the job names or address space names. So here are the jobs or address spaces that are responsible for generating CPU in MQ. So let’s go ahead and add that to our dashboard.

All right. We looked earlier at command rates, so switch over there. If we look at the CICS data, one way we can slice it is by a region name. When we do that here, we’re doing to see two different profiles. We’ve got this first set of regions that does a lot of gets. And then the remaining regions are just doing puts. Supplementing that data, the accounting data also differentiates between gets and puts with and without data. And so here, the channel initiator workload, there has a significant number of gets that don’t return a message. And so, you know, that may be due to a get weight that’s expiring.