1. Mainframe Adapter for SNA Reference Guide
  2. Application-to-Application Programming Examples
  3. CPI-C Programming Examples
  4. ATMI Conversational Client to Host CPI-C, Server Gets Control

2.3.4 ATMI Conversational Client to Host CPI-C, Server Gets Control

Figure 2-24 DMCONFIG File Entry


DMCONFIG File Entry

  1. ATMI client invokes toupsrv service.
  2. The toupsrv service issues tpconnect for SIMPCPIC, which is advertised in the DM_REMOTE_SERVICES section of the DMCONFIG file. The TPRECVONLY indicates the server gains control and the first conversation verb the toupsrv can issue is tprecv. Data is sent on the tpconnect in the idata buffer.
  3. The remote service with tpname TPNCPIC invokes TOUPCPIC program.
  4. The server accepts the conversation with the cmaccp call. The conversation ID returned on the request in convid is used for all other requests on this conversation.
  5. The cmrcv request receives the idata buffer contents for processing.
  6. The TOUPCPIC program processes data.
  7. The cmsst request prepares the next send request by setting the send type to CM_SEND_AND_FLUSH.
  8. The cmsend command returns the obuffer contents into the client tprecv odata buffer. The data is immediately flushed on the send request.
  9. The cmdeal request ends the conversation.

Parent topic: CPI-C Programming Examples