2.3 CPI-C Programming Examples

The examples in this section show the protocol exchanges between the local ATMI platform and remote host application program. The type of ATMI service request determines the nature of the client/server communication model. For requests initiated by the host application, the configuration information for the local service determines the protocol exchanges on the conversation.

Although it is most suited for the DPL environment, the tpcall is usually used in the DPL environment but can also be used for a request/response to an APPC server.

The examples in this section represent a few of the many programming scenarios available for using CPI-C and ATMI service invocations. These examples employ the most natural and efficient approaches.

• ATMI Client Request/Response to Host CPI-C
  
• ATMI Client Asynchronous Request/Response to Host CPI-C
  
• ATMI Client Asynchronous Request/Response to Host CPI-C with No Reply
  
• ATMI Conversational Client to Host CPI-C, Server Gets Control
  
• ATMI Conversational Client To Host CPI-C, Client Retains Control
  
• ATMI Conversational Client to Host CPI-C, Client Grants/gets Control
  
• Host CPI-C to ATMI Asynchronous Request/Response Server with No Reply
  
• Host CPI-C to ATMI Server Request/Response
  
• Host CPI-C to ATMI Conversational Service, Client Retains Control
  
• Host CPI-C ATMI to Conversational Service, Client Grants Control
  
• Transactional ATMI Client Request/Response to Host CPI-C
  
• Transactional Host CPI-C to ATMI Conversational Server, Client Grants Control
  
• Transactional ATMI Conversational Client to Host CPI-C, Server Gets Control