The back-end transaction fails to start

It is possible that the back-end transaction fails to start. However, APPC contains a transmission delay mechanism that informs the front-end transaction of the failure when the conversation has been active long enough for responses from the back-end system to have been received. The front-end transaction is informed of this by way of a TERMERR condition in response to a DTP command. EIBERR, EIBFREE, and EIBERRCD are set (see Checking the outcome of a DTP command for the possible values of EIBERRCD).

Before sending data, the front-end transaction should determine whether the back-end transaction has started successfully. One way of doing this is to issue an EXEC CICS® SEND CONFIRM command directly after the EXEC CICS CONNECT PROCESS command. This causes the front-end transaction to suspend until the back-end transaction has responded or the back-end transaction has sent the failure notification that is described above. EXEC CICS SEND CONFIRM is discussed in Safeguarding data integrity.