2.2.10 Transactional ATMI Conversational Client to CICS/ESA DTP, Server Gets Control

Figure 2-19 DMCONFIG File Entry

1. ATMI client invokes toupsrv service.
2. The toupsrv service issues tpbegin to start the transaction.
3. The toupsrv service issues tpconnect for SIMPDTP, which is advertised in the DM_REMOTE_SERVICES section of DMCONFIG file. The TPRECVONLY indicates the server gains control and the first conversation verb toupsrv can issue is tprecv. Data is sent on the tpconnect in the idata buffer.
4. User transaction DTPS starts TOUPDTPS program.
5. It is recommended you save the EIBTRMID to a program variable. This value may be used to identify the specific conversation on your CICS/ESA APPC verbs.
6. The EXEC CICS RECEIVE command receives the idata buffer contents for processing.
7. The TOUPDTPS program processes data.
8. The EXEC CICS SEND command returns the OUT-BUFFER contents into the clients tprecv odata buffer. CONFIRM indicates that the conversation is finished and is communicated to the tprecv as TPEV_SVCSUCC. INVITE enables the client to respond with a COMMIT request.
9. The toupsrv service issues tpcommit to end the transaction. The COMMIT is received on the EXEC CICS RECEIVE verb and the server issues EXEC CICS RETURN to commit the resources, terminate the transaction, and free the outstanding conversation.