RLS Lock Analysis situation

The single predefined situation in this category monitors RLS resources to identify problems that can degrade performance.

Note: All the attribute names in this group are prefixed with CICSplex_RLS_Lock_Analysis. except where stated.

CICSplex_Held_RLS_Locks

Monitors the existence of locks on RLS resources. It issues an alert whenever it detects a task that is holding an RLS resource. This situation uses attributes from the CICSplex RLS Lock Analysis group. This situation is distributed automatically to the *hub Tivoli Monitoring Server; distribute it to all Tivoli Monitoring Servers where OMEGAMON AI for CICS is running.

Use the RLS Lock Analysis workspace to find any tasks that can be waiting for an RLS lock to become available. If a lock is not being released, use the Transaction Analysis workspace to display the owning task's wait type to determine whether it is looping, waiting on a resource, or deadlocked with another task. You can invoke the CEKL command using the Take Action feature to free the lock and allow waiting tasks to continue. To limit the number of lock conflicts, consider transaction classes.

Formula: If the value of Task_State equals H and the value of Time_in_Suspend_Numeric is greater than or equal to 60 then situation CICSRegion_Held_RLS_Locks is true.