|
Guys, Ive developed a web app in WDSC for deployment on WAS 4.0 Advanced. This app uses dbbeans to access the database via WAS defined datasources using connection pooling provided by the toolbox driver com.ibm.as400.access.AS400JDBCConnectionPoolDataSource . I have gone through the pain barrier and this db access is mostly working. This all works on WDSC, but I have come up against a problem when I deploy to WAS 4.0. When I want to access the local AS400, I use datasource defined using the db2 native access provided by com.ibm.db2.jdbc.app.DB2StdConnectionPoolDataSource. To allow me to use standard library list I set naming=system. For some reason this property works fine with the toolbox driver, but seems to be ignored by native driver. Does anyone know why, and if there is a way round this. Ive tried naming=sys, naming = system, naming=*SYS, still no joy. Cheers Colin.W For the latest on Bertram Books products and services and for up-to-the-minute book news visit www.bertrams.com This e-mail and any attachments may contain information that is confidential and privileged and is solely for the use of the intended recipient. If you are not the intended recipient please notify the sender and delete this e-mail and any attachments immediately
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.