Re: My CCSID is set to 65535 (was Print and email a file in the IFS)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've been in exactly that situation at my last two employers. Both
times, I changed the system value to ccsid 37, and I've never had a
problem (from that ;)). Since your language setting implies a ccsid of
37, data in the database is consistent with it, even though it is stored
as binary data. Once you change the system value, new tables take on the
new settings. Old tables are left as is. Of course, YMMV. I'd try the
test system first and let things settle for a few weeks.

Pete Hall
pbhall@xxxxxxxxxxxxx


Glenn Gundermann wrote:

Eric (& others),

I know I've seen a lot of posts about CCSID but I haven't paid much
attention to them. For some reason, this posting stuck out a bit more.

<snip>

Make sure your QCCSID system value is not 65535, as this setting disables
much of the data conversion that is supposed to occur when exporting data
to the IFS.

<snip>

As it turns out, I'm on two system (test/development & production) that
are both set with QCCSID to 65535.

If I DSPJOB, I see:
Coded character set identifier . . . . . . . . . : 65535
Default coded character set identifier . . . . . : 37

I'm not sure what these two do.(?)

What, if anything, is not going to work properly?

Everything seems to be working that I know of.
Should I be worried about something or bring this up with anyone?
Is there a strong reason to change the system value?
What, if anything, will stop working if this is changed?

Tks,

Glenn Gundermann
ggundermann@xxxxxx
(647) 272-3295

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHYzVipcZsDl8OX6kRApXrAKC9Z1JVKiz6y+ThXuY2sWd6pAKSRwCgnMqs
YPHKd+dZXqamqMdlS5KjQsQ=
=9ZOn
-----END PGP SIGNATURE-----