J2EE Application in WebSphare AIX - datasource DB2 OS390

GroupIT - Jenny Kuan Kong Lang

J2EE Application in WebSphare AIX - datasource DB2 OS390
Problem: J2EE Application running in a WebSphere V5.0.2 environment on AIX V5, accessing DB2 V5.0.2 data residing on OS/390 V2.10 via DB2 Connect V8.1.

In the test environment, connectivity is no problem whether via WebSphere or via DB2 CLP.
In the production environment, however, connectivity is still not a problem via DB2 CLP.
However when testing connection via WebSphere Admin Console TEST CONNECTION button it failed with error
" 505970e6 DataSourceCon E DSRA8040I: Failed to connect to the DataSource. Encountered : java.lang.UnsatisfiedLinkError: SQLConnect at COM.ibm.db2.jdbc.app.DB2Connection.connect(DB2Connection.java(Compiled Code)) at COM.ibm.db2.jdbc.app.DB2Connection.<init>(DB2Connection.java:424) at COM.ibm.db2.jdbc.app.DB2ReusableConnection.<init> (DB2ReusableConnection.java:69) at COM.ibm.db2.jdbc.DB2PooledConnection.getConnection(DB2PooledConnection.java:188) at com.ibm.ws.rsadapter.DSConfigurationHelper.testConnectionForGUI DSConfigurationHelper.java:1712) at java.lang.reflect.Method.invoke(Native Method) at com.ibm.ws.management.DataSourceConfigHelperMBean.testConnectionToDataSource2 (DataSourceConfigHelperMBean.java:511) at com.ibm.ws.management.DataSourceConfigHelperMBean.testConnection (DataSourceConfigHelperMBean.java:439) at java.lang.reflect.Method.invoke(Native Method)...."

Both DB2 Connect and WAS are on the same machine.
The only difference is that DB2 Connect on the test environment was installed for 32-bit architecture, whilst DB2 Connect on the production environment for 64-bit.

Has anybody come across this problem.

rgds
Jenny Kuan

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Leon Katsnelson

Re: J2EE Application in WebSphare AIX - datasource DB2 OS390
(in response to GroupIT - Jenny Kuan Kong Lang)
If you are indeed connecting to DB2 for OS/390 V5 database on the mainframe
and using DB2 Connect V8.1 then you are using:
1. an unsupported version of DB2 as DB2 for OS/390 V5.1 is out of service
and
2. using a version of DB2 Connect that does not support V5 of DB2 for
OS/390

I also want to say that this is not just "it is not officially supported
but it still works" statement. Certain functions in DB2 Connect V8.1 really
will not work with V5 of DB2 for OS/390. You have 2 choices:
1. continue to use DB2 Connect V7.2 (still sold and fully supported) or
2. upgrade DB2 for OS/390 to a supported version i.e. V6.1, 7,1 or 8.1

If I misunderstood your environment (quite possible), let me know.

Leon Katsnelson. Manager, DB2 Product Management and Planning. Admin
Assistant: Susanne Mcfarlane (905) 413-3632
"Things should be made as simple as possible, but not any simpler." --
Albert Einstein



GROUPIT - Jenny
Kuan Kong Lang
<[login to unmask email] To
.MY> [login to unmask email]
Sent by: DB2 Data cc
Base Discussion
List Subject
<[login to unmask email] J2EE Application in WebSphare AIX -
ORG> datasource DB2 OS390


01/04/2004 09:30
PM


Please respond to
DB2 Database
Discussion list
at IDUG






Problem: J2EE Application running in a WebSphere V5.0.2 environment on AIX
V5, accessing DB2 V5.0.2 data residing on OS/390 V2.10 via DB2 Connect
V8.1.

In the test environment, connectivity is no problem whether via WebSphere
or via DB2 CLP.
In the production environment, however, connectivity is still not a problem
via DB2 CLP.
However when testing connection via WebSphere Admin Console TEST CONNECTION
button it failed with error
" 505970e6 DataSourceCon E DSRA8040I: Failed to connect to the DataSource.
Encountered : java.lang.UnsatisfiedLinkError: SQLConnect at
COM.ibm.db2.jdbc.app.DB2Connection.connect(DB2Connection.java(Compiled
Code)) at
COM.ibm.db2.jdbc.app.DB2Connection.<init>(DB2Connection.java:424) at
COM.ibm.db2.jdbc.app.DB2ReusableConnection.<init>
(DB2ReusableConnection.java:69) at
COM.ibm.db2.jdbc.DB2PooledConnection.getConnection(DB2PooledConnection.java:188)
at com.ibm.ws.rsadapter.DSConfigurationHelper.testConnectionForGUI
DSConfigurationHelper.java:1712) at java.lang.reflect.Method.invoke(Native
Method) at
com.ibm.ws.management.DataSourceConfigHelperMBean.testConnectionToDataSource2
(DataSourceConfigHelperMBean.java:511) at
com.ibm.ws.management.DataSourceConfigHelperMBean.testConnection
(DataSourceConfigHelperMBean.java:439) at
java.lang.reflect.Method.invoke(Native Method)...."

Both DB2 Connect and WAS are on the same machine.
The only difference is that DB2 Connect on the test environment was
installed for 32-bit architecture, whilst DB2 Connect on the production
environment for 64-bit.

Has anybody come across this problem.

rgds
Jenny Kuan
---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". If you will be out of the office, send the
SET DB2-L NO MAIL command to [login to unmask email] The IDUG List
Admins can be reached at [login to unmask email] Find out the
latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm