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

2.3.12 Transactional Host CPI-C to ATMI Conversational Server, Client Grants Control

Figure 2-32 DMCONFIG File Entry


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 cmssl sets the conversation attributes to sync-level 2 with CM_SYNCPOINT. This allows the ATMI service to participate in the transaction.
  4. The cmallc request initiates the advertised service mapped to MIRRORSERV in the DM_LOCAL_SERVICES section of the DMCONFIG file.
  5. The MIRRCPIC causes the client to relinquish control to the ATMI server with a prepare-to-receive request. The cmsptr sets the prepare-to-receive type to CM_RECEIVE_AND_FLUSH. The cmptr request immediately relinquishes control.
  6. The MIRROR service sends the data contents of the odata buffer to the cmrcv ibuffer. The cmrcv receives a confirm request from the server indicating the conversation should be terminated.
  7. The client replies positively to the confirm request with cmcfmd.
  8. The MIRRCPIC client prepares to free the conversation with the cmdeal request. The conversation in CM_DEALLOCATE_SYNC_LEVEL commits all updated resources in the transaction and waits for the SAA resource recovery verb, srrcmit. After the commit sequence has completed, the conversation terminates.

Parent topic: CPI-C Programming Examples