DSNL031I csect-name DRDA EXCEPTION CONDITION IN RESPONSE FROM SERVER LOCATION=location-indicator FOR THREAD WITH LUWID=luwid REASON=reason-code ERROR ID=error-id CORRELATION ID=correlation-id CONNECTION ID=connection-id IFCID=ifcid SEE TRACE RECORD WITH IFCID SEQUENCE NUMBER=seq-no
Explanation
A DRDA exception condition was detected in response data returned from the application server (AS). Possible error conditions include:
- An error reply message and severity code received from the server.
- A parsing error detected while processing a reply message or reply data object
- A DRDA protocol violation, (for example, an object returned that is not valid for this command).
- csect-name
- The name of the control section that issued the message.
- luw-id
- The logical unit of work (LUW) ID that identifies the thread. This values is also included in the trace record.
- location-indicator
- An indicator of the location:
- The server's relational database name
- The server's VTAM® LU name
- The server's IP address
- reason-code
- The DB2® reason code for this specific error.
- error id
- The module name concatenated with a 4-byte source id that uniquely determines the source within the module where the exception is encountered.
- correlation-id
- The correlation identifier of the thread that detected the DRDA exception condition. Correlation IDs beginning with 001 through 028, inclusive, identify system agents.
- connection-id
- The connection name of the thread that detected the DRDA exception condition.
- ifcid-number
- The IFCID number of the trace record that was written.
- sequence-number
- The IFCID sequence number associated with the trace record. The
trace record contains information that can be used to determine what
caused the DRDA exception condition,
and is written to the destination for IFCID 191. The message and the
trace record are written only the first time an error is detected.
This avoids flooding the console and the trace. The sequence number
is printed in hexadecimal.
If the sequence number is zero, then the trace data was not externalized.
System action
An alert was generated. Additionally, if the seq-no is not zero, the system wrote a trace record with IFCID=ifcid-name to the destination for IFCID 191 that can be used to diagnose the problem.
Problem determination
Determine the destination of the trace record and locate and print the trace record with SEQUENCE NUMBER=sequence-number. The description of the reason code can be used in conjunction with the publication Distributed Relational Database Architecture™ Reference to determine the type of DRDA exception that has been detected. Determine the problem and which system is responsible by using the procedures that are described in Obtaining DB2 Diagnosis Guide and Reference.
