I think there is a problem using the .../ext folder - what is in there
will always be processed - my memory is weak here, but Scott recommended
it in his early stuff, then gave revised recommendations to use a
So I think you are always going to get the old driver - get everything
out of .../ext as soon as you can - everything of your own, that is.
Here is something from a wiki article - it mentions /jre/lib/ext -
that's where you put the original driver -
The virtual machine searches for and loads classes in this order:
1. bootstrap classes: the classes that are fundamental to the Java
the public classes of the Java Class Library
>, and the private
classes that are necessary for this library to be functional).
2. extension classes: packages
> that are in the
/extension/ directory of the JRE <https://en.wikipedia.org/wiki/JRE
or JDK <https://en.wikipedia.org/wiki/JDK
3. user-defined packages and libraries
By default only the packages of the JDK
> standard API
extension packages are accessible without needing to set where to find
them. The path for all user-defined packages
> and libraries must be set
in the command-line (or in the Manifest
> associated with the Jar
On 9/28/2015 10:14 AM, Gerald Magnuson wrote:
I have apps that use the jdbc apps that Scott built (JDBCR4).
my driver file (mysql-connector-java-5.1.7-bin.jar) is quite old, and I
want to use a new driver:
my CLASSPATH is : "/QIBM/UserData/Java400/ext/"
I put the new driver in a new place (/QIBM/UserData/Java400/extTEST/)
I then changed my *JOB envvar to the new path.....
but how do I know if it is using the new driver?
I ask because I also changed my *JOB envvar to a invalid path (instead of
extTEST, I used extxxxxx), and it also worked fine.
by worked, the sql query ran fine...