2.2.9 Transactional ATMI Client Request/Response to CICS/ESA DTP

Figure 2-18 DMCONFIG File Entry

Note:

This is not the recommended method of performing a DTP transactional service. Please refer to the transactional DPL using request/response for the recommended method.

1. ATMI client toupclt invokes toupsrv service. (Note that each tpcall made in the program must be bookended with a tpbegin and a tpcommit.)
2. The service issues tpbegin to start a transaction.
3. The toupsrv service issues tpcall for SIMPDTP, which is advertised in the DM_REMOTE_SERVICES section of the DMCONFIG file.
4. User transaction DTPS starts TOUPDTPS program.
5. Save the EIBTRMID to a program variable. This value is 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-BUUFER contents into the clients odata buffer. CONFIRM indicates the conversation is finished. INVITE allows 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.