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, Client Grants/gets Control

2.3.6 ATMI Conversational Client to Host CPI-C, Client Grants/gets Control

Figure 2-26 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.
  3. The remote service with tpname TPNCPIC invokes TOUPCPIC program.
  4. The server accepts the conversation with the cmaccp request. The conversation id returned on the request in convid is used for all other requests on this conversation.
  5. The cmrcv requests receives the indicator that control has been granted to the server.
  6. The cmsend request returns its obuffer contents into the first client tprecv odata buffer. The data may not immediately be sent.
  7. The cmsend request returns its obuffer contents into the second client tprecv odata buffer. The data may not immediately be sent.
  8. The cmptr request flushes the data to the client, and grants control to the client.
  9. The cmrcv request receives the tpsend idata buffer contents for processing. The TPRECVONLY is passed to the tprecv, relinquishing control of the conversation.
  10. The cmdeal indicates a successful completion of the conversation to the tprecv; no data is passed.

Parent topic: CPI-C Programming Examples