2.1.7 Transactional ATMI Client Multiple Requests/Responses to CICS/ESA DPL

Figure 2-7 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 SIMPDPL, which is advertised in the DM_REMOTE_SERVICES section of the DMCONFIG file. The tpcall is requested multiple times within the same transaction.
4. Host mirror transaction starts TOUPDPLS program and passes idata buffer contents for processing. The host mirror transaction remains as a long-running task to service all further requests on the transaction.
5. The TOUPDPLS program processes data.
6. The CICS/ESA system returns the commarea into the client’s odata buffer.
7. Step 3 through Step 6 are repeated until the toupsrv service loop end conditions are met.
8. The tpcommit request indicates the successful completion of the transaction, causing a commit of its own resources and the resources held by the host mirror transaction.