Db2 DRDA exception condition reason codes

In most cases, Db2 provides a 32-bit reason code as the common token sent to all destinations to be notified of the DRDA exception condition.

Db2 requester role

If the DRDA exception condition is identified at the Db2 AR, then the reason code is placed within the SQLERRD1 field within the SQLCA. Additionally, the reason code is externalized within the detailed data, subfield X'82', subvector X'96' (WHY) of the Tivoli® NetView for z/OS® alert and the IFCID 0191, 0192, 0193, 0194 and 0195 trace records. This reason code is directly traceable to an SQL statement that is issued by an application. It is the common token that identifies the alert and all relevant trace records produced. The reason code is the starting point for the DRDA exception condition diagnosis.

Db2 database server role

If the DRDA exception condition is identified at the Db2, then the reason code is placed within the server diagnostic information scalar, included within the DDM reply message that is returned to the requester. The reason code is externalized within the detailed data, subfield X'82', subvector X'96' (WHY) of the Tivoli NetView for z/OS alert and the IFCID 0191 trace records. This reason code is directly traceable to a DDM command that is received from the AR. It is the common token that identifies the alert and all relevant trace records produced. The reason code is the starting point for the DRDA exception condition diagnosis.