CICS monitoring data for determining task rule thresholds

You can use CICS® monitoring data to determine an appropriate threshold to set for a policy task rule.

Table 1 lists which items of CICS monitoring data you can use to determine an appropriate threshold for each supported CICS policy task rule type. The field names of the monitoring data items are nicknames and might not be unique, so the field IDs are also listed. If you are administering CICS systems of mixed releases, be aware that some task rules are not supported by the policy function in older releases of CICS. The CICS release number shown by the field name of a performance data item indicates the earliest release that item was supported by the policy function. If omitted, the release number is CICS TS V5.1.
Table 1. CICS monitoring data used to determine a task rule threshold
Rule type Rule subtype Performance data group Performance data item
Field name Field ID
Async request RUN TRANSID command DFHTASK ASRUNCT V5.4 471
Database request DLI command DFHDATA IMSREQCT V5.3 179
SQL command DFHDATA DB2REQCT 180
EXEC CICS request EXEC CICS command DFHCICS EICTOTCT V5.3 402
File request DELETE command DFHFILE FCDELCT 040
READ command DFHFILE FCGETCT 036
READ NEXT command DFHFILE FCBRWCT 038
READ PREVIOUS command DFHFILE FCBRWCT 038
READ UPDATE command DFHFILE FCGETCT 036
REWRITE command DFHFILE FCPUTCT 037
START BROWSE command DFHFILE See  1   
WRITE command DFHFILE FCADDCT 039
IBM MQ request MQ command DFHDATA WMQREQCT V5.3 395
Named counter request GET COUNTER command DFHCICS NCGETCT V5.3 464
Program request LINK command DFHPROG PCLINKCT 055
Start request START command DFHTASK ICPUINCT V5.2 059
Storage allocation 24-bit shared storage allocated DFHSTOR SC24GSHR 145
24-bit task storage allocated DFHSTOR
SCUSRHWM
    +
SC24CHWM
See  2 
033

116
31-bit shared storage allocated DFHSTOR SC31GSHR 148
31-bit task storage allocated DFHSTOR
SCUSRHWM          
    +
SC31CHWM
See  2 
106

119
64-bit shared storage allocated DFHSTOR SC64GSHR 446
64-bit task storage allocated DFHSTOR
SC64CHWM          
    +
SC64UHWM
See  2 
442

444
Storage request 24-bit shared storage request DFHSTOR SC24SGCT 144
24-bit task storage request DFHSTOR
SCUGETCT            
    +
SCCGETCT
See  2 
054

117
31-bit shared storage request DFHSTOR SC31SGCT 147
31-bit task storage request DFHSTOR
SCUGETCT            
    +
SCCGETCT
See  2 
105

120
64-bit shared storage request DFHSTOR SC64SGCT 445
64-bit task storage request DFHSTOR
SC64CGCT            
    +
SC64UGCT
See  2 
441

443
Syncpoint request SYNCPOINT command DFHSYNC SPSYNCCT V5.2 060
TD queue request READQ TD command DFHDEST TDGETCT V5.2 041
WRITEQ TD command DFHDEST TDPUTCT V5.2 042
Time CPU time DFHTASK USRCPUT 008
Elapsed time DFHTASK USRDISPT V5.2 007
TS queue bytes WRITEQ TS command Transaction resource class data
MNR_TSQUEUE_PUT_AUX_ITEML V5.2
    +
MNR_TSQUEUE_PUT_MAIN_ITEML V5.2
    +
MNR_TSQUEUE_PUT_SHR_ITEML V5.3
See  3 		  
WRITEQ TS AUXILIARY command Transaction resource class data
MNR_TSQUEUE_PUT_AUX_ITEML V5.2
See  3 		  
WRITEQ TS MAIN command Transaction resource class data
MNR_TSQUEUE_PUT_MAIN_ITEML V5.2
See  3 		  
WRITEQ TS SHARED command Transaction resource class data
MNR_TSQUEUE_PUT_SHR_ITEML V5.3
See  3 		  
TS queue request READQ TS command DFHTEMP
TSGETCT V5.2                
    +
TSGETSCT V5.3
044

460
WRITEQ TS command DFHTEMP
TSPUTACT V5.2            
    +
TSPUTMCT  V5.2            
    +
TSPUTSCT V5.3
046

047

461
WRITEQ TS AUXILIARY command DFHTEMP TSPUTACT V5.2 046
WRITEQ TS MAIN command DFHTEMP TSPUTMCT V5.2 047
WRITEQ TS SHARED command DFHTEMP TSPUTSCT V5.3 461
Notes:
  1. There is no monitoring data item for the number of STARTBR requests. You can calculate the number of STARTBR, ENDBR, RESETBR, and UNLOCK file control requests by subtracting the file request counts, FCGETCT, FCPUTCT, FCBRWCT, FCADDCT, and FCDELCT from the total file request count, FCTOTCT. In most cases, half of this value would be a reasonable approximation for the number of STARTBR requests.
  2. The total number of these two fields gives a worst-case high water mark for storage consumed by a task in a given DSA (24-bit, 31-bit, or 64-bit).
  3. Transaction resource class data is produced for each temporary storage queue accessed by a task. To determine an appropriate policy threshold for a task, add the corresponding counts for each queue to get an aggregate number of bytes written to all temporary storage queues of a given type (auxiliary, main, or shared) by a task.