What happens if the back-end transaction fails to start

It is possible that the back-end transaction fails to start. However, because of the transmission delay mechanism in APPC, the front-end transaction is not informed of this fact until the conversation has been active long enough for responses from the back-end system to be received.

The front-end transaction is informed of this via CDBERR and CDBFREE. In addition, CDBERRCD is set as shown in Table 1.

Table 1. Some indications of back-end failure
CDBERRCD value Reason
10086032 The PIP data sent with the GDS CONNECT PROCESS was incorrectly specified.
10086034 The partner system does not support basic conversations.
080F6051 The partner transaction failed security check.
10086041 The partner transaction does not support the sync level requested on the GDS CONNECT PROCESS.
10086021 The partner system does not recognize the requested transaction identifier.
084C0000 The partner system cannot start the partner transaction.
084B6031 The partner system is temporarily unable to start the partner transaction.

Before sending data, the front-end transaction should find out whether the back end transaction has started successfully. One way of doing this is to issue a GDS SEND CONFIRM command directly after the GDS CONNECT PROCESS. This causes the front-end transaction to be suspended until the back end transaction has responded or the back-end system has sent the failure notification as described.



dfhp6c0050.html | Timestamp icon Last updated: Monday, 5 June 2017