Re: Native JDBC Driver for v5r3

[Keith.McCully@xxxxxxxxxxxx]

The runtime error was caused by the job CCSID set to 65535. Changed to 37 
and the connection worked!

As this is a new box, I'll have to check the other system values, eg. our 
country is set to US but we're based in UK. 

One puzzle is that the CCSID is also set to 65535 on our old v4r3 AS400 
and JDBC worked with db2_classes.zip?

Just to recap:

1. The OS400 supplied /QIBM/ProdData/OS400/jt400/lib/jt400Native.jar added 
to the classpath appears to work fine.
Not used JTOpen version of jt400Native.jar or any other jars for this 
purpose.

2. Class.forName("com.ibm.db2.jdbc.app.DB2Driver")- UNCHANGED

3.Use DriverManager.getConnection("jdbc:db2:*local", properties)for the
connection. - UNCHANGED

A big thanks to all who responded

Keith
  -----Original Message-----
From: Keith.McCully@xxxxxxxxxxxx [mailto:Keith.McCully@xxxxxxxxxxxx]
Sent: 18 May 2005 12:12
To: Java Programming on and around the iSeries / AS400
Subject: Native JDBC Driver for v5r3


Hi,


Just taken delivery of new iSeries with OS v5r3 & JVM 1.4.2. Previously,
had OS v4r3 & JVM 1.1.7 and JDBC worked ok.

Since both my programs and data are on the iSeries, I've followed IBM's
recommendation and opted for the "Native" JDBC driver.

So far I have the following:

1. Added /QIBM/ProdData/OS400/jt400/lib/jt400Native.jar to my classpath 
(as
my OS > v5r1) 
2. Class.forName("com.ibm.db2.jdbc.app.DB2Driver")
3.Use DriverManager.getConnection("jdbc:db2:*local", properties)for the
connection.

Points 2 & 3 are unchanged from the previous version that worked, only the
classpath has changed.

Compiled and tested in Qshell. Compiles ok but get runtime error message
when attempts to establish connection:

Caught exception: INTERNAL ERROR:  Creation of DB2Driver object for
registering with DriverManager failed.

Any help or suggestions would be appreciated,

Keith