and to clairify, my CLASSPATH is:

Name . . . . . . . . . : CLASSPATH

Value . . . . . . . . . :

On Tue, Sep 29, 2015 at 10:51 AM, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx

Yes, the older version off jTDS works with older versions of Java, that's
why this solves the problem. (You seem very surprised by this?)

I would not recommend ever putting stuff in the "ext" directory... The
reason is because anything in that directory is _always_ loaded, and you
can't override it with the CLASSPATH variable. This prevents you from
being able to test different versions of the classes in different job, for

But, that's a separate issue from the unsupported class version issue.

On 9/29/2015 10:38 AM, Gerald Magnuson wrote:

I found that I am working again IF I put the origional, old jar
(jtds-1.2.5.jar) back into the /QIBM/UserData/Java400/ext/

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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