The predefined situations in this category monitor transactions across CICS regions and the z/OS images that the CICSplex spans. A description and formula for each of these situations follow.
A CICS transaction can be using more CPU than normal. If the Transaction Analysis workspace indicates that the processor time associated with a transaction is rising rapidly, the task can be in a loop. Looping transactions can be terminated automatically using one of the following actions:
Formula
If the value of CPU_Time is greater than 0.500 and the value of CPU_Time is less than or equal to 1.000 then situation CICSplex_TranCPUTime_Warning is true.
A CICS transaction can be using more CPU than normal. If the Transaction Analysis workspace indicates that the processor time associated with a transaction is rising rapidly, the task can be in a loop. Looping transactions can be terminated automatically using one of the following actions:
Formula
If the value of CPU_Time is greater than 1.000 then situation CICSplex_TranCPUTime_Critical is true.
The predefined situations in this category monitor transactions across CICS regions and the z/OS images that the CICS spans. A description and formula for each of these situations follow.
Formula
If the value of Transaction_ID equals DSNC and the value of Status equals inactive then situation CICSRegion_Tran_DSNC_Inactive is true.
Formula
If the value of CPU_Time is greater than 1 then situation CICSRegion_Tran_Elapsed_CPU is true.
See also the CICSplex Transaction Analysis attribute group.