home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC75667 Status: Closed

DB2 LUW INCORRECTLY SENDING QRYNOPRM UPON RECEIVE CNTQRY FROM ZOS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 zOS client calling a stored procedure on DB2 LUW server 
encounters a DSNL031I error. This is due to the DB2 LUW server 
sending a QRYNOPRM (query not open reply message) upon receiving 
a CNTQRY (continue query) call that was made by the DB2 zOS 
client when calling the stored procedure. Collecting DB2 DRDA 
traces will allow one to observe the CNTQRY and QRYNOPRM calls.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 z/os clients working with DB2 LUW servers users          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 LUW incorrectly sending QRYNOPRM upon receive CNTQRY     * 
* from zOS                                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.7 FP5.                                         * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem fixed in v9.7 FP5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.04.2011
19.01.2012
19.01.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList