Dependent Regions situations
You can identify the exceptions that occur when dependent regions are in specific states.
- IMS_DepReg_Long_Lock_Wait
- This situation triggers for a dependent region when one or more
dependent regions are waiting for an IRLM or PI lock and the lock
wait elapsed time is equal to or greater than one second.
The formula is:
Dependent_Regions.Lock_Elapsed_Time GE 1 AND Dependent_Regions.Region_Status EQ Wait-IRLM OR Dependent_Regions.Region_Status EQ Wait-PIENQ - IMS_DepReg_OTMA_ACK/NAK_Warning
- This situation triggers for a dependent region when an OTMA TPipe
is waiting for an ACK or NAK for a commit-then-send, CM0, output response.
If this event persists, investigate the OTMA client to determine why
an ACK/NAK response is not occurring or is taking too long.
The formula is:
Dependent_Regions.OTMA_Status_WAITH EQ True OR Dependent_Regions.OTMA_Status_WAITA EQ True - IMS_DepReg_Occupancy_High
- The dependent region identified by this exception has been identified
as being utilized 100.00%. Perhaps additional regions must be started.
The formula is:
Dependent_Regions.Region_Occupancy_Percentage EQ 100The event workspace for the IMS_DepReg_Occupancy_High situation supports a link to the IMS Dependent Region Locking Conflict in Classic workspace which displays lock conflicts for the selected region in the Classic interface and a link to the IMS Console in Classic workspace which displays OCMD or ICMD in the Classic interface configured to stop the current transaction in the selected region.
- IMS_DepReg_Occupancy_Low
- The dependent region identified by this exception has been identified
as being utilized 0.00 %. Perhaps this region can be stopped.
The formula is:
Dependent_Regions.Region_Occupancy_Percentage EQ 0 - IMS_DepReg_Swapped_Out
- The dependent region identified by this exception is currently
swapped out of memory. The will cause delays the next time the dependent
region is needed since all of it's pages will need to be brought back
into main storage. If the performance of the applications using this
region is critical, then you might want to consider making this region
non-swappable.
The formula is:
Dependent_Regions.Residence_Status EQ SwappedOut - IMS_Held_Locks_Warning
- The total number of locks held has exceeded the threshold. When
the lock held count becomes too high, it increases the chances that
there will be lock contention and therefore causes performance degradation.
If one application is consuming most of the locks, you might want
to verify that the application is not in a state where it cannot release
the locks it currently holds.
The formula is:
Dependent_Regions.Locks_Held_Count GE 8 AND Dependent_Regions.Locks_Held_Count LT 10 - IMS_Held_Locks_Critical
- The total number of locks held has exceeded the threshold. When
the lock held count becomes too high, it increases the chances that
there will be lock contention and therefore causes performance degradation.
If one application is consuming most of the locks, you might want
to verify that the application is not in a state where it cannot release
the locks it currently holds.
The formula is:
Dependent_Regions.Locks_Held_Count GE 10