DB2 FOR LUW / DB2FORLUW / 970 - DB2

When the SP referencing a insensitive scrollable cursor on z/os 
is called , the o/p may be incomplete and clp client might 
report SQL30020N error. The problem is seen when the size of 
rows is large and z/os server returns the partial rowset in the 
first buffer. When csm drives a fecth request for fetching the 
remaining rows on the continue query(CNTQRY), it sends a request 
for 1 row fetch. But accroding to DRDA rules, server expects the 
number to be equal to pending rows that are unfetched on the 
server. 
 
Explanation from crm page -> crm number:75296,005,000 
 
A previous CNTQRY command specified a QRYROWSET parameter, which 
indicated the number of rows to be returned as a rowset. Because 
of the blocking limits in effect with the requester, only a 
partial rowset was returned to the requester. Some rows in the 
requested rowset are still unfetched and are pending. The DRDA 
rules require that this subsequent CNTQRY command must either: 
 
Specify a QRYROWSET value that is equal to the number of pending 
rows in the rowset. Reset the query blocks from the pending 
rowset. 
 
The CNTQRY command did not specify the QRYRSTBLK parameter to 
reset the query blocks, so this command is assumed to completes 
the pending rowset. Because the requested QRYROWSET value does 
not equal the number of pending rows in the rowset that was 
requested by the previous CNTQRY, a DRDA exception occured.

**************************************************************** 
* USERS AFFECTED:                                              * 
* CLP users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When the SP referencing a insensitive scrollable cursor on   * 
* z/os                                                         * 
* is called , the o/p may be incomplete and clp client might   * 
*                                                              * 
* report SQL30020N error.                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v97fp4 or later                                   * 
****************************************************************

N/A

DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 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
 

Problem fixed.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

27.07.2010
28.04.2011
28.04.2011

9.7.FP4