DB2 on zOS issues:

Issue:

When you have a websphere cluster which uses DB2 on z/OS as its datastore and due to a machine upgrade happening the subsystem ID for this DB2 needs to be changed (say for example DB1P to DBP1.)

Issue Fix:

Change the following files,

wkplc_comp.properties
wkplc_dbtype.properties
icm.properties

on all nodes in the cluster and then change the data source for the cluster in the deployment manager.

Data Source Configuration Issue:

Environment:
WPS6.2
WAS6.1

Issue:
While trying 'test connection' on a data source,it results in following error:

The test connection operation failed for data source SCA Application Bus ME data source on server nodeagent at node localhostNode01 with the following exception: java.sql.SQLException: [jcc][t4][10205][11234][3.52.110] Null userid is not supported. ERRORCODE=-4461, SQLSTATE=42815DSRA0010E: SQL State = 42815, Error Code = -4,461. View JVM logs for further details.

Solution:
Set the Component Managed Authentication Alias to the proper level.
This alias is used for database authentication at run time.
The Component-managed Authentication Alias is only used when the application resource reference is using res-auth = Application.

If your database (for example, Cloudscape) does not support user ID and password, then do not set the alias in the component-managed authentication alias or container-managed authentication alias fields. Otherwise, you see the warning message in the system log to indicate that the user and password are not valid properties. (This message is only a warning message; the data source is still created successfully.)

If you do not set an alias (component-managed or otherwise), and your database requires the user ID and password to get a connection, then you receive an exception during run time.

IHS Frequently asked Questions:

IHS-FAQ's