2.3.9 Host CPI-C to ATMI Conversational Service, Client Retains Control

Figure 2-29 DMCONFIG File Entry

1. The CPI-C application program MIRRCPIC is invoked using environment start-up specifications.
2. The MIRRCPIC client requests cminit to establish conversation attributes and receive a conversation id that will be used on all other requests on this conversation. The remote server and service are named in the CPI-C side information entry MIRRSIDE.
3. The cmallc request initiates the advertised service mapped to MIRRORSERV in the DM_LOCAL_SERVICES section of the DMCONFIG file.
4. The cmsend request sends the contents of obuffer to the ATMI service in the tpsvcinfo->data buffer.
5. The cmdeal request flushes the data and ends the conversation, as indicated by TPNOREPLY in the tpsvcinfo->flag field.