OTMA situations
You can take correct action when OTMA flood conditions occur.
- IMS_OTMA_TIBs_In_Use_Critical
- This situation triggers when the percentage of Transaction Instance
Blocks (TIBs) in use for a TMember is 80% or higher. Corrective action
might be needed in order to prevent an OTMA flood condition which
occurs when the number of TIBs in use is 100%. TMember input is rejected
until the flood condition is relieved. TIB growth can occur due to
a stopped program, unavailable message region, message arrival rate
exceeds processing rate, or failure to generate a CM1 IOPCB response
leaving orphaned TIBs.
The formula is:
OTMA_TMember.TIB_Used_Percent GE 80.00 - IMS_OTMA_TIBs_In_Use_Warning
- This situation triggers when the percentage of Transaction Instance
Blocks (TIBs) in use for a TMember is between 70% and 80%. Corrective
action might be needed to prevent an OTMA flood condition which occurs
when the number of TIBs in use is 100%. TMember input is rejected
until the flood condition is relieved. TIB growth can occur due to
a stopped program, unavailable message region, message arrival rate
exceeds processing rate, or failure to generate a CM1 IOPCB response
leaving orphaned TIBs.
The formula is:
OTMA_TMember.TIB_Used_Percent GE 70.00 AND VALUE OTMA_ TMember.TIB_Used_Percent LT 80.00 - IMS_OTMA_TMember_In_Flood
- This situation triggers when an OTMA TMember is in a flood condition.
A flood condition occurs when the percentage of Transaction Instance
Blocks (TIBs) in use for a TMember reaches 100%. Corrective action
must be taken to relieve the flood condition as input is rejected
for the TMember until the condition is relieved. TIB growth can occur
due to a stopped program, unavailable message region, message arrival
rate exceeds processing rate, or failure to generate a CM1 IOPCB response
leaving orphaned TIBs.
The formula is:
OTMA_TMember.User_Status EQ Flood - IMS_OTMA_TPipe_Output_Que_High
- This situation triggers when the output queue count for a TPipe
exceeds the indicated threshold.
The formula is:
OTMA_TPipe.CQueue_Count GE 20 - IMS_OTMA_TPipe_Stopped
- This situation triggers when a TPipe is stopped. A stopped TPipe
has a status of stopped or input stopped. Determine why the TPipe
has a stopped status and restart the TPipe.
The formula is:
OTMA_TPipe.Status_STOPPED EQ Yes OR VALUE OTMA_TPipe.Status_Stop_Input EQ Yes - IMS_OTMA_TPipe_Wait_ACK_NAK
- This situation triggers when a TPipe is waiting for an ACK or
NAK for a commit-then-send, CM0, output response. If this event persists
for the TPipe, the OTMA client should be investigated to determine
why an ACK or NAK response is not occurring or taking too long.
The formula is:
OTMA_TPipe.Status_WAITA EQ Yes OR VALUE OTMA_TPipe.Status_WAITH EQ Yes