A handy guide on Class Max Task statistics (CST9)
JanakiS 27000496GC Visits (3980)
TXSeries for Multiplatforms allows your transactions to be grouped under different transaction classes. Each transaction class (a.k.a TRANCLASS) can have its own settings for the number of maximum active tasks and the purge limit. If you are interested in runtime statistical information about the tasks executed in a region based on TRANCLASS, then the CICS supplied transaction CST9 is for you.
TXSeries for Multiplatforms V8.1 introduces support for unlimited number of TRANCLASS definitions through the new TCD stanza, removing the limit of 10. When you run CST9 to get Class Max Task statistics, you will observe that it has a scroll up/down facility to accommodate any number of TRANCLASS entries.
Let's spend a few minutes to understand the fields listed by CST9. Rows listed correspond to different entries in the TCD stanza (TRANCLASS entries). Columns listed are as below:
Values in the columns 3,4,5 and 6 are reset, whenever statistics counter is reset.
Looking for an example? Here is one for you.
TranClass=TCL1 (Assume TRN1 to be long running).
TranClass TCL1 in TCD stanza:
MaxActive=2 (this means that only 2 tasks under this TRANCLASS can be active at a time).
PurgeThresh=2 (this means that only one task can be in waiting state).
Table 1 discusses a few scenarios and CST9 values for each of them.
Table 1: Scenarios and corresponding CST9 values
With CST9 (Class Max Task statistics), task scheduling can be monitored closely for each transaction class. Based on the observations from CST9, you can dynamically revise the MaxActive and PurgeThresh values for a TRANCLASS using CEMT SET TRANCLASS(...) MAXACTIVE(...) | PURGETHRESH(...).