DB2 - Problem description
Problem IC66996 | Status: Closed |
V97 BIND OPTION CONCURRENTACCESSRESOLUTION IS NOT PUSHED DOWN TO Z/OS | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The bind API in v97 level of code prevents the passdown of the bind option CONCURRENTACCESSRESOLUTION to DB2 for z/OS V10. DB2 z/OS has started supporting CURRENTLY COMMITTED behavior in v10, including beta versions which are now available. GA will be available in August, which is before the next fixpak of DB2 LUW. Any programs requiring an override of CURRENTLY COMMITTED behavior that use DB2 LUW v97 client are UNABLE to bind the packages for their SQL application. This means they are unable to ensure compatibility with existing cursor stability semantics, which is a regresion. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * user with LUW client and DB2 Z/OS 10.1 as server * **************************************************************** * PROBLEM DESCRIPTION: * * When CONCURRENTACCESSRESOLUTION is specified with LUW Client * * to z/oS v10 Server. The Option will not flow to z.os server * * v10. * **************************************************************** * RECOMMENDATION: * * Upgrade to product db2_v97fp2 GA * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
The complete fix for this problem first appears in DB2 UDB Version 9.7 FixPak 2. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.03.2010 23.03.2010 23.03.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |