DB2 FOR LUW / DB2FORLUW / 910 - 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:                                              * 
* Problem occurs when the server is Z/os and a SP with         * 
* insensitive scrollable cursor is called                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When a SP referencing a insensitive scrollable cursor on     * 
* Z/os server is called from clp client, error is reported.    * 
* Problem was that when csm requested rows from server upon    * 
* second fetch, it updated incorrect rowset size. Since we did * 
* not match what server was expecting, error was thrown by     * 
* server.                                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to product ficpack v91fp10                           * 
****************************************************************

N/A

DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows
 

The problem has been fixed.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC70222 IC70223 IC70224 
follow-up : 

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

26.07.2010
14.06.2011
14.06.2011

9.1.FP10