PQ78724: WITH W501000, WHEN A NEW DATA SOURCE IS ADDED, DEFAULT ACTION IS REQUIRED FOR CUSTOM PROPERTY "CURRENTSQLID" | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description With service level W501000 ("cumulative fix"), when a new data source is added via the Admin Console or scripting, by default, the Custom Property "currentSQLID" has a null default value. Until this apar ships, the customer must take an action of (a) filling in the currentSQLID Custom Property to make use of the currentSQLID functionality, (b) blank the value for the property out, or (c) remove the property from the data source. This is not outlined by the steps in the ++ HOLD for ACTION for the PTFs associated with service level W501000. When this APAR is delivered, these steps will no longer be required and the default value for currentSQLID when defining a new data source will not require the customer to take additional action.Local fix Follow the ++ HOLD for ACTION for the PTFs associated with service level W501000 for actions to take when defining a new data source until this apar is available.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: The default value of the Custom * * Property currentSQLID on the DB2 390 * * Local JDBC Provider (RRS) is invalid * * and causes -204 and -553 errors when * * using the Data Source. * **************************************************************** * RECOMMENDATION: * **************************************************************** The default value of the currentSQLID property on the DB2 390 Local JDBC Provider (RRS) is the empty string rather than null, which causes WebSphere to attempt to set the DB2 value of CURRENT SQLID using an empty string. If this Data Source is used to obtain a Connection and the primary authorization id that is used is not a DB2 admin, you will see an SQL -553 error similar to the following in the joblog of your application servant region: DB2JDBCSection Received Error in Method execute_immediate: SQLCODE==> -553 SQLSTATE ==> 42503 Error Tokens ==> <<DB2 7.1 SQLJ/JDBC>> If this Data Source is used to obtain a Connection and the primary authorization id that is used is a DB2 admin, the Connection will be successfully obtained, but an SQL -204 error similar to the following will appear in the joblog of your application servant region when you use the Connection with unqualified SQL (in particular, note that the referenced table will have a blank table qualifier): DB2JDBCCursor Received Error in Method prepare:SQLCODE==> -204 SQLSTATE ==> 42704 Error Tokens ==> <<DB2 7.1 SQLJ/JDBC>> .IOPProblem conclusion The code that processes the currentSQLID Custom Property has been changed to detect an increased number of invalid values and to ignore them rather than passing them on to DB2 as the CURRENT SQLID. APAR PQ78724 is associated with SERVICE LEVEL W501001 of WebSphere Application Server V5.0 for z/OS.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
|
Document Information |
Current web document: swg1PQ78724.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 #: PQ78724
IBM Group: Software Group
Modified date: Nov 2, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.