MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2013

RE: RESOLVED: SQL-inconsistent results using XMLELEMENT, XMLSERIALIZE, XMLCONCAT



fixed

I miss the old days of just ASCII vs EBCDIC. Where if you knew the hex
code of the data you knew what the heck it was. Now it's the hex code of
the data plus what the column, table or file's coded character set id is.
Oh well, that genie isn't going back into the box. IBM has some
redbook(s) on globalization and whatnot you can look at.

You can try following the language id specified on SET OPTION
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/db2/rbafzsoption.htm
You may want to read the link right there for globalization as my
perspective is English should be good enough for everyone and I wouldn't
want you to bury this in your code only to find out you've just shot
yourself in the foot.

But, again, somewhere on your system you have the default at 65535.
CHGSYSVAL QCCSID is something many of us have ran midday with no ill
effects. Oh, somewhere is a Chuck Pence caveat on why that is evil, but
I'll leave the manual labor of looking that up to you.


Rob Berendt





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact