PQ74700: PROVIDE SQLID SUPPORT FOR WEBSPHERE FOR Z/OS 5.0

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
In the case of DB2 390 local datasources, the capability to
specify an SQLID that is to be used to set the current SQLID
which will be used to control the use of unqualified table
references in an  application will not be available at GA. This
capability was supported for DB2 390 local datasources in
WebSphere z/OS 4.0.1 and will be added to WebSphere z/OS 5.0
with this APAR.  Until this APAR is implemented, the current
SQLID associated with a DB2 390 datasource connection will be
defaulted as follows:
1) To the userid specified on a getConnection(userid,password)
    request when res-auth=Application.
.
2) To the authentication userid (i.e., owner userid) that is
    associated with the datasource when it is defined to
    WebSphere z/OS.  This userid and the password specified
    with it will be passed to the DB2 datasource when getting
    a connection and will be used as the owner of the
    connection.  Because the authentication userid associated
    with a datasource can now be specified by the installation
    when it defines a DB2 390 local datasource, it is possible
    for an installation to exercise control over the SQLID in
    this way.
.
3) If no authentication user id is specified when a DB2 390
    local datasource is defined, then the userid associated
    with the current environment (e.g., current thread or
    address space) will be used to establish connection
    ownership. This userid will then be the default SQLID.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Add SQLID support for DB2 390 Local.    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
User should be able to supply a value for the current SQLID,
which will be used by DB2 to qualify unqualified SQL.
Problem conclusion
Added a Custom Property to the DB2 390 Local Data Source called
"currentSQLID".  If the user leaves this untouched, function
will remain the same.  If the user provides a value here, the
value that they supplied will be set as the CURRENT SQLID on
every DB2 connection obtained with this resource.  The rules
for what value can be used for this property are the same as
the DB2 rules for what values can be set as the CURRENT SQLID.


APAR PQ74700 is associated with SERVICE LEVEL W501000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ74700
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-05-30
Closed date 2003-09-18
Last modified date 2003-10-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF BBOZ3800 BBOZ3801      

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ80305    UP03/09/25 P F309

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ74700.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ74700
IBM Group: Software Group
Modified date: Oct 3, 2003