PQ53749: RUNNING OUT OF DB2 CONNECTIONS USING GLOBAL TRANSACTION

APAR status
Closed as duplicate of another APAR.

Error description
Customer is running application in WebSphere 4.0 z/OS
environment where there is a lot of DB2 connections occurring
in a global transaction.  The eventually hit the maximum
number of connections from JDBC to DB2 and receive an
ABEND0C2 failure.  The same code runs fine in the
distributed WebSphere environment.  They would like the code
to run unmodified on z/OS.  They need this fix to be delivered
as shortly after the availability of 4.01 as possible.
Usinsg shared connections in a global transaction raises
data integrity issues.  WebSphere for z/OS took the position
to protect the user from these issues by not allowing
the shared connections.  This was deemed necessary on the z/OS
platform due to the fact that many z/OS customers will be
mixing new and legacy applications having different objects
possibly mapping to the same row in a database.  A switch
needs to be established to allow the customer to make the
decision on whether resource sharing is allowed for an
application.
Local fix Problem summary Problem conclusion Temporary fix Comments
The problem reported by APAR PQ53749 has been fixed in APAR

PQ55873.
APAR information
APAR number PQ53749
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED DUB
PE NoPE
HIPER NoHIPER
Submitted date 2001-10-19
Closed date 2002-03-18
Last modified date 2002-03-18

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ53749
IBM Group: Software Group
Modified date: Mar 18, 2002