I suspect the problem is that the IASP information was removed from the
user profile. I believe the default is to use the IASP associated with the
user profile. If you want to set it in the JDBC application, you can use
the "database name" connection property when connecting using the JDBC URL.

On Wed, Oct 4, 2017 at 9:06 AM, Blalock, Bill <Bill.Blalock@xxxxxxxxxxxxx>
wrote:

The problem seems to be caused by a CPF2110 error (Library not found). I
found the error in the QZDASOINIT job log, just prior to the SQL0204 error
reported by the Java exception.

This behavior began after upgrading from V7R1 to V7R3.

The library is in a user ASP. It appears that the DB2 JDBC is now
searching SYSBASE and not the user ASP for the library.

Question 1: Is there a setting on the AS400 which would effect this
behavior?

Question 2: From Java how do you control the ASP wich DB2 JDBC searches?

Thanks all

The information contained in this message is proprietary and/or
confidential. If you are not the intended recipient, please: (i) delete the
message and all copies; (ii) do not disclose, distribute or use the message
in any manner; and (iii) notify the sender immediately. In addition, please
be aware that any message addressed to our domain is subject to archiving
and review by persons other than the intended recipient. Thank you.
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/java400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.