Re: charset problems with db/400

Yes, that is what solved a similar problem for me.  Look at the problem file, 
and the
problem fields and see what the CCSID is.  If it is something other than 37, 
putting
translate binary=true will force binary to be translated to text.  I accessed 
some files in
JD Edwards and for some reason, the text fields had been set to a different 
CCSID.

Kristen

Tim Kosacek wrote:

> Hard to say without knowing more detail about what you are doing, but try
> setting the driver property "translate binary=true"  (this is from memory so
> you might want to check the docs).
>
> -----Original Message-----
> From: java400-l-bounces@midrange.com
> [mailto:java400-l-bounces@midrange.com]On Behalf Of Timur Evdokimov
> Sent: Saturday, February 01, 2003 4:49 PM
> To: 'Java Programming on and around the iSeries / AS400'
> Subject: charset problems with db/400
>
> Hello,
>
> I've come across very strange problem.
> If Java program runs at iSeries and uses type 2 JDBC from
> db2_classes.jar to access tables, string operands are updated with
> really weird strings, like "...,.,,." (or even worse) instead of
> specified value. Of course when subseqent select(s) are trying to
> retrieve this data, it doesn't work.
>
> The same update from STRSQL console is pretty OK
>
> The same Java code on the same iSeries with type 4 JDBC (from JT400) is
> also OK
>
> The same Java code on other AS/400s is sometimes OK, but sometimes not.
> But when the database with problems is copied through SAVF to another
> AS/400 where it is OK, it _is_ OK.
>
> Can anyone say anything?
>
> Thanks,
> Timur