00D35E5D

Explanation

Acting as a requester or a server, Db2 has detected an error while parsing a DRDA object. The final length computed by parsing the object using its descriptor is larger than the stated length of the object itself.

System action

An alert is generated and message DSNL031I (if the error is detected by Db2 acting as a requester) or message DSNL032I (if the error is detected by Db2 acting as a server) is written to the console. Refer to the description of this message for further information.

Operator response

Notify the system programmer.

System programmer response

If you suspect an error in Db2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.

Problem determination

Analyze the statistics class 4 trace record identified by the IFCID sequence number enumerated in the DSNL032I message. For the Db2 system generating the DSNL032I message, collect the following diagnostic items:
  • Statistics Class 4 trace record for the LUWID associated with the failing request.
In addition, identify all connected systems participating in the processing of the remote request. This includes the requester system to which the application is connected and the data server which is the target of the remote request. This may also include intermediate server systems. For each system that is a Db2 system, collect the following diagnostic items:
  • Console output and the listing of the SYSLOG data set from each connected site for the period of time spanning the failure.

For non-Db2 systems, refer to the documentation specific to those products for diagnostic procedures.

If any dumps were generated on any Db2 system participating in processing the remote request, collect the following diagnostic items:
  • Listings of the SYS1.LOGREC data set, obtained by executing IFCEREP1 at each connected site.
  • All dumps created by this failure.