Writing programs for APPC mapped conversations
These topics describe the CICS® APIs available for DTP programming using APPC mapped conversations.
- Conversation initiation
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 remote system. - Back-end transaction initiation
The back-end transaction is initiated as a result of the front end transaction’s CONNECT PROCESS command. - Transferring data on the conversation
These topics discuss how to pass data between the front- and back-end transactions, and provide a program fragment illustrating the commands described and the suggested response code checking. - Communicating errors across a conversation
The APPC mapped API provides commands to enable transactions to pass error notification across a conversation. - Safeguarding data integrity
If it is important to safeguard data integrity across connected transactions, then the CICS synchronization commands should be used. - Ending the conversation
A conversation can end in two ways, unexpectedly, or under transaction control. - Checking the outcome of a DTP command
Checking the response from a DTP command can be separated into three stages. - Summary of CICS commands for APPC mapped conversations
The CICS application programming interface provides a set of commands for use in APPC mapped conversations. - State transitions in APPC mapped conversations
These topics shows the state transitions that occur when transactions engage in APPC mapped conversations under the EXEC CICS API.
dfhp60o.html |
Last updated: Monday, 5 June 2017