Writing programs for MRO conversations

These topics describe the CICS® APIs available for DTP programming using MRO conversations.

Initiation of an MRO conversation
The front-end transaction is responsible for acquiring a session, specifying the conversation characteristics and requesting the startup of the back-end transaction in the partner system.
Initiation of the back-end transaction in an MRO conversation
The back-end transaction is initiated either by an attach header received from the partner system or by a transaction identifier included in the incoming data, and is started with the session as its principal facility.
Transferring data on the MRO conversation
This topic discusses how to pass data between the front-end and back-end transactions.
Safeguarding data integrity for MRO conversations
If it is important to safeguard data integrity across connected transactions, you can use the synchronization commands.
Ending the MRO conversation
To end a transaction, one transaction issues a request for termination and the other receives this request. When this has happened, the conversation is unusable and both transactions must issue a FREE command to release the session.
Checking the outcome of a DTP command
Checking the response from a DTP command can be separated into three stages.
Summary of commands for MRO conversations
The CICS application programming interface provides a set of commands for use in MRO conversations.
State transitions in MRO conversations
State transitions occur when transactions engage in MRO conversations. The state transitions are presented in the form of a state table. The state table shows which commands a transaction can issue while the conversation is in any given state. It also shows how the conversation state changes as a result of any command.

Parent topic: Developing distributed applications