Re: Native JDBC Driver for v5r3

    Hi Keith,

    Here's the support information that explains it:

IBM eServer iSeries Support: Software Technical Document : 29290926
"Character Conversion Errors with Job CCSID 65535"

<
http://www-912.ibm.com/s_dir/slkbase.NSF/0/9ea41ee0c6099d1e86256caa006e4b59?OpenDocument
>

and everyone should probably look through

iSeries Memorandum to users V5R3

<
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/info/rzaq9.pdf
>

which also mentions the change.

    The first document says " A Job CCSID value of 65535 should not be
used," which is very nice since that's how the system is shipped.  We first
came across this on a Saturday when a client ( who swore they tested on
another box ) planned to go to production on that Monday ( tested our 24/7
support claim! ).

    My first inclination was to set QCCSID to the code page value for
QCHRID, which would resolve things systems wide, but we didn't know what
impact that might have on the other third-party products on the system ( the
client uses a lot of imaging. )  Our solution for getting things running was
to CHGJOB to CCSID 37 ( we are US based ) in the calling CL programs.  That
works, but is very unsatisfactory to me.

    I discussed a resolution to the whole 65535 mess with the AS/400 I18N
guy at COMMON in 1997, but here we are, still doing custom work at every
installation, and another barrier to Java implementation.  And we are seeing
too many divergences between the native and type 4 JDBC drivers.


                                                         Joe Sam

Joe Sam Shirah -        http://www.conceptgo.com
conceptGO       -        Consulting/Development/Outsourcing
Java Filter Forum:       http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International?    http://www.jguru.com/faq/I18N
Que Java400?            http://www.jguru.com/faq/Java400


----- Original Message ----- 
From: <michael@xxxxxxxxxxxxxxxxxx>
To: "Java Programming on and around the iSeries / AS400"
<java400-l@xxxxxxxxxxxx>
Sent: Wednesday, May 18, 2005 10:34 AM
Subject: RE: Native JDBC Driver for v5r3


> V5R3 is the release where IBM broke everything...err...fixed
> everything...by enforcing CCSID.
>
>
> > -------- Original Message --------
> > Subject: Re: Native JDBC Driver for v5r3
> > From: Keith.McCully@xxxxxxxxxxxx
> > Date: Wed, May 18, 2005 10:21 am
> > To: <java400-l@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
> > --