DFS1988W OTMA input messages from member yyyyyyyy have reached xx% of the maximum active input message limit zzzz
Explanation
OTMA internally creates a Transaction Instance Block (TIB) to track each active input message from a member. A maximum number of TIBs can be specified by OTMA descriptor, client-bid protocol message, or /START TMEMBER INPUT command. The active or queued input message from member yyyyyyyy is reaching xx percent of the limit indicated by zzzz. This message is issued at 80% of TIB limit and every 5% thereafter. Potentially, an OTMA message flood condition exists.
To view the current limit, issue the /DISPLAY TMEMBER command.
System action
IMS OTMA continues to process new input messages with less storage.
Programmer response
Determine whether the dependent regions are active to process input messages, whether the remote transactions insert back to the I/O PCB, and whether the OTMA clients are flooding the IMS. You might need to control or stop the OTMA clients to prevent the flood conditions. Ensure that the IMS regions are started to run the OTMA transactions. You can use the /DISPLAY TMEMBER TPIPE command to display the input message counts. If needed, contact your IMS system programmer for assistance.