Terminating conversational transactions in OTMA

Occasionally, you might need to terminate a conversational transaction in OTMA, either to cleanup a message on a tpipe queue after a conversation hangs or for some other reason.

A conversational transaction might hang, for example, if the OTMA client that initiated the conversation terminates without IMS detecting the termination. In such a case, the storage associated with the hung transaction, such as the storage required for a transaction instance block (TIB) and a scratchpad area, is not freed. Over time, if hung transactional conversations are not terminated, the amount of storage that is wasted on them can become significant.

You can use one of the following options to terminate hung conversational transactions.

Specify the ENDCONV= parameter of the DFSOTMA descriptor in the DFSYDTx member of the IMS PROCLIB data set.
If the conversational transaction remains idle for the specified period of time after the prior iteration of the conversational transaction completes, OTMA ends the transaction and releases IMS resources that were allocated for the transaction.
Use the QUERY OTMATI and /EXIT CONV commands:
1. Issue the IMS type-2 command QUERY OTMATI specifying the SHOW(ALL) keyword and the name of one or more tmembers, tpipes, or both.
2. In the output of the QUERY OTMATI command in the CONVID column, note the conversational ID of the transaction instances that have a message age value in the MsgAge column that is large enough to indicate a hung conversational transaction.
3. After identifying the transaction instance and noting its conversational ID, issue the /EXIT CONV conv_id TMEMBER tmembername TPIPE tpipename command.