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 Retains Control

2.3.5 ATMI Conversational Client To Host CPI-C, Client Retains Control

Figure 2-25 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 TPSENDONLY indicates the client retains control and continues to send data. No data is sent with the tpconnect.
  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 tpsend idata buffer contents for processing. The conversation is relinquished with the TPRECVONLY flag.
  6. The TOUPCPIC program processes data.
  7. The cmsend returns a response in the tprecv idata buffer, along with notification from the cmdeal command that the conversation is over. The cmdeal flushes the data buffer and the tprecv reevent parameter is set to TPEV_SUCCESS.

Parent topic: CPI-C Programming Examples