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 report 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: a situation with a CEKL action to terminate a transaction that exceeds a CPU threshold, or the Resource Limiting function of Tivoli OMEGAMON XE for CICS on z/OS or manually using the KILL command.
Formula
If the value of the attribute CPU_Time is greater than 0.500 and the value of the attribute CPU_Time is less than or equal to 1.000
A CICS transaction can be using more CPU than normal. If the Transaction Analysis report 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: a situation with a CEKL action to terminate a transaction that exceeds a CPU threshold, or the Resource Limiting function of Tivoli OMEGAMON XE for CICS on z/OS or manually using the KILL command.
Formula
If the value of the attribute CPU_Time is greater than 1.000
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 attribute Transaction_ID equals DSNC and the value of attribute Status equals inactive then situation CICSRegion_Tran_DSNC_Inactive is true.
Formula
If the value of attribute CPU_Time is greater than 1 then situation CICSRegion_Tran_Elapsed_CPU is true.
See also the CICSplex Transaction Analysis attribute group.