DSNL032I csect-name DRDA EXCEPTION CONDITION IN REQUEST FROM REQUESTER LOCATION=location-indicator FOR THREAD WITH LUWID=luw-id REASON=reason-code ERROR ID=error-id IFCID=ifcid-number SEE TRACE RECORD WITH IFCID SEQUENCE NUMBER=sequence-number
Explanation
A DRDA exception condition was detected while processing a command or command data received from the application requester (AR). Possible error conditions include errors detected while processing a command or a command data object.
- csect-name
- The name of the control section that issued the message.
- location-indicator
- An indicator of the location:
- The requester's relational database name
- The requester's VTAM® LU name
- The requester's IP address
- luw-id
- The logical unit of work (LUW) ID that identifies the thread. This value is also included in the trace record, or "NETID.LUNAME.000000000000" if the error detected involves an invalid FMH5.
- 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 was encountered.
- 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.
Operator response
Notify the system programmer for analysis.
System programmer response
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.
