RE: JDBC does not know CCSID=65535?

Files with CCSID of 65535 are created when you do CRTPF ... RCDLEN(xxx).
According to IBM, these files are interpreted as if they contain hexadecimal
data, or something like that.  They seem to feel that this is a feature and
not a bug.  At least with Client Access there's a checkbox in the Properties
of the download object where you can turn off this "feature".  There may be
a JDBC connection property you can specify to do that too, but I can't find
where I put that list.  It's available somewhere online, maybe somebody can
point you to it.

PC2

-----Original Message-----
From: Bruce Jin [mailto:brucej@MRC-PRODUCTIVITY.COM]
Sent: April 6, 2001 10:09
To: JAVA400-L@midrange.com
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
+---