Analysis of selected CICS Statistics and Transaction timing metrics relative to T8 TCBs which the CICS Dispatcher uses to dispatch Java programs which are zIIP eligible.
More CICS Statistics Videos
- Assessing CICS Storage Health
- Assessing CICS Transaction & Enqueue Health
- CICS Transaction Class Metrics
- CICS TCB Dispatcher Metrics – Part 1
- CICS TCB Dispatcher Metrics – Part 2 (T8 TCBs)
What you might have noticed here real quick is also that the number of T8 TCBs is much higher for this group of regions. And the documentation tells us that those are used by CICS for Java programs. So again, if we look at the peak TCBs that are in use and look at that set of regions by TCB mode, there are those T8 TCBs, and we can look at those across a broader time interval. And let’s go ahead and look at it kind of over a month interval, and when we do that for this type of TCB, we see lots of increases of the numbers at many different times across many different days, and not just at that one interval that we’ve been looking at. So, the CICS statistics data provides extensive metrics on how the dispatcher is managing each of the many types of TCBs within the regions and the CICS transaction data captures CPU time for each TCB type at the transaction level, which we’re going to see shortly. We can also view the groups of regions where zIIP eligible work is executing.
And you might remember that this matches the CICS group we saw earlier in the statistics data with many T8 TCBs in use. And I mentioned at that time that CICS uses T8 TCBs for Java programs, which are zIIP eligible. So let’s see if I was telling the truth, right? Let’s make note of the primary transactions here in that group that are using zIIP. And so DWRU, DWR1, DWWU and then let’s explore how those transactions stack up on CPU consumed on the T8 TCB. So I’m going to go ahead and capture that in the dashboard.
All right, so let’s look at the CPU view by transaction, and we want to look at the actual CPU time. We want to focus particularly on that T8 TCB time. So let’s remove all the other types of TCB time. And when we do that, we see that sure enough, it’s those same three transactions that we saw earlier in that CICS group that are the ones that are consuming the T8 TCB. So that correlates with what we saw on the zIIP CPU time as well.
Speak to a Technical Expert Today
Whether you are conducting product research, need support on a project, are experiencing downtime, or want to learn more about how IntelliMagic can support your business, our experts are here to help.
You May Also Be Interested In:
Best Practices in CICS Performance Analysis (Transactions and Statistics) | IntelliMagic zAcademy
This session will introduce you to several best practices for enhancing your analysis of CICS Transaction and Statistics data.
Analysis of CPU By Plan: CICS Transaction (110.1) and Db2 Accounting (101) Part 2
Integrated visibility between Db2 Accounting and CICS Transaction data can correlate CICS transaction IDs driving high CPU in Db2 with the CICS profile of the transaction.
Elapsed Time Profiles by Correlation ID: CICS Transaction (110.1) and Db2 Accounting (101) Part 1
This video shows how viewing CICS Call Attach work by Correlation ID enables both CICS and Db2 teams to view elapsed time profiles within Db2 corresponding to each CICS transaction ID.