00D35E6B

Explanation

Db2 has detected an error while parsing a DDM SNDPKT command received from a remote requester. The SNDPKT command contains an invalid RDBNAM instance variable. Long variable name support has been negotiated but the RDBNAM value length either exceeded the 255 byte limit or was too short.

System action

An alert is generated and message DSNL032I is written to the console. Refer to the description of this message for further information.

A DDM reply message (SYNTAXRM) is returned to the remote requester.

Operator response

Notify the system programmer.

System programmer response

This is most likely an error at the remote requester system. If you suspect an error in Db2, see the information about identifying and reporting problems in Searching for known problems and solutions for Db2 for z/OS.

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.