IMS conversations and OTMA

OTMA-to-IMS conversations are send-then-commit and are nonrecoverable.

IMS creates a unique conversation ID for each transaction pipe that is saved in the Server token field in the OTMA state-data section of the message. This ID must be passed to IMS with all subsequent client input for the conversation using that transaction pipe.

The server-state flag is set to Conversational State in the state-data section of the message prefix when IMS acknowledges the transaction. This flag must be set for all subsequent client input during the conversation.

An IMS conversation can be terminated by issuing the /EXIT command. Alternatively, if a client wants to terminate the IMS conversation, the client can send a message with the commit-confirmation flag set in the message-control information section of the message prefix (indicating a deallocate flow). IMS then terminates the IMS conversation. A deallocate flow must specify Conversational State for the server-state flag in the state-data section of the message prefix; it must also set the server token field.