Re: AS400JDBCDriver Issues (NGay@xxxxxxxxxxxxx)

Thanks Nigel. 

Unfortunately, that is not he cause on this occasion.  The QCCSID is set
at 37 on our system and when running the job, it shows that it is using
CCSID of 37.

Regards
John Herbert
EDS
 
date: Thu, 20 Apr 2006 08:30:59 -0230
from: NGay@xxxxxxxxxxxxx
subject: Re: AS400JDBCDriver Issues

John,

I may have an answer for the first problem.  Is the QCCSID system value
on
your iSeries set to 65535?  (i.e. check DSPSYSVAL QCCSID).

If so, then V5R3 no longer allows the native JDBC driver to make
database
connections from jobs with CCSID 65535.  We ran into the same problem
upgrading from V5R2 -> V5R3.  We were using the native driver directly
so
there was an obvious error in the job log about it.  I'm not sure what
error you may or may not see when trying use the native JDBC driver via
the
Toolbox driver and specifying driver=native.

It didn't cause us a huge amount of grief because we already planned to
get
everything moved across to using the Toolbox driver anyway (and the
toolbox
driver still works connecting from jobs with CCSID 65535).  If you must
use
the native driver, the solutions I'm aware of are:

1) Change the job description of however you are running the Java
program
to specify a valid CCSID
2) After the job starts, issue a CHGJOB CCSID(x) to specify a valid
CCSID
before starting the Java pgm
3) Change the QCCSID system value

There's info about it in:

http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzaq9/rzaq9.
pdf
(see at bottom of page 24)

Can't help at all on the second problem I'm afraid, I've never used
batch
updates.

Hope this helps,

Nigel Gay,
Computer Patent Annuities.