PM22017: CURRENTSQLID DOES NOT WORK PROPERLY WHEN THE DATASOURCE USES IBM DATA SERVER DRIVER. CEIDS0058E

Fixes are available

APAR status

Closed as program error.

Error description

It is possible that the schema name indicated by the
CurrentSQLID property is not honored.  One consequence is that
customers may encounter the following error due to an incorrect
schema name:

 Exception data: com.ibm.ejs.container.CreateFailureException: ;
nested exception is:
.com.ibm.events.datastore.DataStoreException: CEIDS0058E
Database table cei_t_properties does not exist for schema
WPJMSU. The defau lt data store is unable to start.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 users that configures Common    *
*                  Event Infrastructure with DB2 z/OS database *
*                  using IBM Data Server Driver.               *
****************************************************************
* PROBLEM DESCRIPTION: The automatic configuration process     *
*                      of Common Event Infrastructure with     *
*                      DB2 z/OS database does not support      *
*                      specifying a different schema from      *
*                      the CURRENTSQLID when the data source   *
*                      uses IBM Data Server.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The automatic configuration process of Common Event
Infrastructure with a DB2 z/OS database creates the WebSphere
Application Server data source based on the DB2 Universal JDBC
Driver Provider (XA) driver version (the case of remote DB2
z/OS database) or DB2 Universal JDBC Driver Provider (the case
of local DB2 z/OS database). These are the scenarios when JDBC
driver v3.0 is used and in this case the user can specify a
different schema where the tables are stored on. At runtime
the tables will be qualified with the correct schema. In case
of a data source that is based on the IBM Data Server driver
the tables are not correctly qualified. The user that is
specified for the connection is used instead.

Problem conclusion

The runtime code used when the initial database access is
performed was augmented in order to consider a different
schema if this is specified. This can be achieved by providing
a value tot the CURRENTSQLID custom parameter.
In order to support this also at the configuration level, the
automatic configuration process with DB2 z/OS database has been
changed by adding to the configEventServiceDB2ZOSDB
configuration Admin Task a new optional parameter
-jdbcDriverVersion that will accept the following
possible/acceptable values 3.0 / 4.0
By using the '3.0' value it will configure the JDBC provider
to use DB2 Universal JDBC Driver Provider (XA) or DB2
Universal JDBC Driver Provider. The usage of '4.0' value will
determine the configuration of the JDBC provider to be based
on the DB2 Using IBM JCC Driver (XA) or on the DB2 Using IBM
JCC Driver version (depending on the database location  &#162;&#226;&#130;&#172;&#226;&#156;
remote or local).
The introduced behavior is:
a. -jdbcDriverVersion not specified in the AdminTask - The
configuration will be performed using 'DB2 Universal JDBC
Driver Provider (XA)' or DB2  &#162;&#226;&#130;&#172; &#156;Universal JDBC Driver Provid
therefore the 3.0 driver version.
b. -jdbcDriverVersion specified but no value supplied - Will
raise an exception as -jdbcDriverVersion needs a parameter,
then if the user goes so far as to use the parameter but does
NOT supply a value, we give an error stating like in the
following example "CEIIN0739E No value was specified for the
jdbcDriverVersion parameter".
c. -jdbcDriverVersion specified with the '3.0' value supplied
- The configuration will be performed using 'DB2 Universal
JDBC Driver Provider (XA)' or DB2 'Universal JDBC Driver
Provider'.
d. -jdbcDriverVersion specified with the '4.0' value supplied
- The configuration will be performed using 'DB2 Using IBM JCC
Driver (XA)' or 'DB2 Using IBM JCC Driver', therefore based
on the provider that supports JDBC 4.0 specification using the
IBM Data Server Driver.
e. -jdbcDriverVersion specified with a value OTHER than 3.0 or
4.0 - Will raise an exception like in the following example:
"CEIIN0701E The parameter jdbcDriverVersion contains the value
<wrong_value>, which is not valid. Valid values are: 3.0, 4.0."

APAR PM22017 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.15 of WebSphere Application Server V7.0.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PM22017
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-09-07
Closed date
2010-11-29
Last modified date
2011-04-04

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UK65060
UP11/03/04 P F103

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.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM22017: CURRENTSQLID DOES NOT WORK PROPERLY WHEN THE DATASOURCE USES IBM DATA SERVER DRIVER. CEIDS0058E

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY UK65060

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

Share your feedback

Need support?