DB2 FOR LUW / DB2FORLUW / 970 - DB2

When the capturedOnly property is set to TRUE, SET SPECIAL 
REGISTER statements or statements with the statementType 
SET_METHOD are not restricted by pureQuery Runtime. The 
statements are always allowed whether or not the statement is in 
the pureQueryXML file. 
 
But in cli co when capturedOnly = TRUE and the SET SQL not found 
in the PDQXML file during run time,  it will throw error, which 
is not suppose to throw error.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Those using CLI Client optimization feature.                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* CLI CO WHEN CAPTUREDONLY = TRUE AND THE SET SQL NOT FOUND IN * 
* THE PDQXML FILE DURING RUN TIME,  IT WILL THROW ERROR.       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v97fp4 or later.                                  * 
****************************************************************

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
 

CLI CO will allow execution of set statements even if it is not 
found in pdqxml file. Fixed in v97fp4.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC72200 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

25.10.2010
28.04.2011
28.04.2011

9.7.FP4