PQ74323: Generate appropriate SQL strings for custom finders when using DB2 390. | |||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Because DB2 390 requires custom SQL, custom finders currently generate incorrect locking semantics.Local fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server Users of * * DB2 390 and custom finders in CMP 1.1. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect locking semantics may be * * used when CMP 1.1 and custom finders * * are used to DB2 390. * **************************************************************** * RECOMMENDATION: * **************************************************************** This is the J2C connection manager part of the fix for the problem, you will need a Fix containing PQ74423 (container) in order for this to work. This is not a firm pre-requisite or co-requisite. Both components function perfectly in the absence of the other's new code, but for the locking semantics to work properly you will need both Fixes.Problem conclusion Between CM and container, we have now corrected the locking sematics for DB2 390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ74323
IBM Group: Software Group
Modified date: May 22, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.