Re: JDBC does not know CCSID=65535?

CCSID 65535 means untranslated or binary data.  If Toolbox or Native JDBC
drivers see this CCSID they flow raw data between the application and the
database.  One use for this tag is for applications that have a mixture of
text and data in a cell.  The app can get the raw data and convert only the
text part because it knows where the text is.  If tagged with a valid ccsid
the jdbc drivers would try to convert the entire cell.  Another use is for
performance critical applications.  If the app thinks it can to a better
job converting data than the driver it can tag a column or DB as 65535.
Then the app is responsible for converting data.

The drivers have a property to override this behavior.  If set, the driver
will convert data assuming it is in the job's ccsid even if a column or DB
is tagged 65535.  From the Toolbox JDBC FAQ:

               Why is the Toolbox JDBC returning EBCDIC characters to my
Java program?

                    Normally, the Toolbox JDBC driver will translate EBCDIC
characters to Unicode Strings automatically. If it
                    appears to be returning untranslated EBCDIC characters
instead, then it is likely that the field in the OS/400
                    database is tagged with CCSID 65535. The Toolbox JDBC
driver recognizes this CCSID as a field that should
                    not be translated. To avoid this behavior, tag fields
on the server that you want to be translated, with a valid
                    CCSID. Alternately, you can set the "translate binary"
connection property to "true", which instructs the JDBC
                    driver to translate all fields, including those tagged
with CCSID 65535. The easiest way to do this is to add
                    ";translate binary=true" to the end of the URL used
when connecting to the database.

David Wall
AS/400 Toolbox for Java


"Bruce Jin" <brucej@MRC-PRODUCTIVITY.COM>@midrange.com on 04/06/2001
12:09:01 PM

Please respond to JAVA400-L@midrange.com

Sent by:  owner-java400-l@midrange.com


To:   <JAVA400-L@midrange.com>
cc:
Subject:  JDBC does not know CCSID=65535?



When I use jdbc on PC to query files on as400, the alpha fields are all
messed up if the file has a ccsid=65535. Files with ccsid=37 are displayed
ok. Why?

I confess I don't know why some of my files have ccsid=65535 and some have
ccsid=37.

Thanks.
Bruce


+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---



+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---