00D35C18
Explanation
Db2 has detected an error while parsing a DRDA BGNBND, BNDSQLSTT, ENDBND, DRPPKG, BNDCPY, BNDDPLY, or REBIND command received from a remote DRDA requester. The DDM object PKGNAM, PKGNAMCSN, or PKGID is invalid.
- PKGNAMCSN
- If the DDM object is PKGNAMCSN, then either the section number is nonpositive (zero or a negative number) or the DDM scalar PKGID contains a package identifier that is greater than 128 bytes in length. Db2 supports package identifiers with a maximum length of 128 bytes.
- PKGNAM or PKGID
- If the DDM object is PKGNAM or PKGID, then the DDM scalar object PKGID contains a package identifier that is greater than 128 bytes in length. Db2 supports package identifiers with a maximum length of 128 bytes.
System action
An alert is generated and message DSNL032I is written to the console.
The DDM reply message VALNSPRM (parameter value not supported) is returned to the local Db2.
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
The statistics class 4 trace record identified by the IFCID sequence number enumerated in the DSNL032I message should be analyzed.
At this local Db2,
collect the following diagnostic items:
- Statistics Class 4 trace record for the LUWID associated with the failing request.
At this Db2 remote
server, collect the following diagnostic items listed in
- Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
- All dumps taken by the attachment facility or requesting application.