CPI-C Reference
- Programs Using CPI Communications to Converse through a Network
- Operating Environment of CPI Communications Program
- Generic Program Interaction with a Distributed Directory
- Program Interaction with CPI Communications and a Distributed Directory
- CRM Interaction with Distributed Security Service
- A Program Using Multiple Outbound CPI Communications Conversations
- A Program Using Multiple Inbound CPI Communications Conversations
- Server Program with Both Inbound and Outbound Conversations
- Commit Tree with Program 1 as Root and Superior
- Data Flow in One Direction
- Data Flow in Both Directions
- The Sending Program Changes the Data Flow Direction
- Changing the Data Flow Direction
- Validation and Confirmation of Data Reception
- Reporting Errors
- Error Direction and Send-Pending State
- Establishing a Full-Duplex Conversation
- Using a Full-Duplex Conversation
- Terminating a Full-Duplex Conversation
- Using Queue-Level Non-Blocking
- Accepting Multiple Conversations Using Blocking Calls
- Accepting Multiple Conversations Using Non-Blocking Calls
- Using the Distributed Directory to Locate the Partner Program
- Establishing a Protected Conversation and Issuing a Successful Commit
- A Successful Commit with Conversation State Change
- Conversation Deallocation Precedes the Commit Call
- LU 6.2 Communications Model
- Creating a TP-Model Application in VM/ESA
- Three Potential Conversation Wrap-Back Scenarios
- Relationship of PFID to Program Installation DNs
- Sample Program Binding Format
- Interactions of Directory Objects
- CPI-C Name Service Interface (CNSI) and CPI Communications
- Program Uses CNSI to Locate PIDN
[ Top of Page | Previous Page | Next Page | Table of Contents ]