2.3.11 Transactional ATMI Client Request/Response to Host CPI-C

Figure 2-31 DMCONFIG File Entry

1. ATMI client invokes toupsrv service.
2. The toupsrv service issues tpbegin to start the transaction.
3. The toupsrv service issues tpcall for SIMPCPIC, which is advertised in the DM_REMOTE_SERVICES section of the DMCONFIG file. Data is sent from the idata buffer on the tpconnect.
4. The remote service with tpname TPNCPIC invokes TOUPCPIC program.
5. The server accepts the conversation with the cmaccp call. The conversation ID returned on the request in convid is used for all other requests during this conversation.
6. The cmrcv request receives the idata buffer contents for processing.
7. The cmsst and cmsptr prepare the next send request by setting the send type to CM_SEND_AND_PREP_TO_RECEIVE and by setting the prepare-to-receive type to CM_PREP_TO_RECEIVE_CONFIRM.
8. The cmsend request immediately returns the obuffer contents into the client’s odata buffer. The server relinquishes control to the server and indicates the end of the conversation with the CONFIRM request.
9. The toupsrv issues the tpcommit to successfully complete the transaction and commit all updated resources. The cmrcv request receives the commit request, and responds explicitly to the request with the SAA Resource/Recovery commit call srrcmit. The conversation is ended after the successful commit exchange.