Mike Schwab wrote: >Of course the ASCII (UTF-8) <=> EBCDIC uses cycles >and causes setup headaches that the rest of the world seems to have >solved with UTF-8.
Um, huh? Db2 Version 5 (generally available in June, 1997) introduced formal ASCII support (CCSID ASCII clause). Db2 has formally supported Unicode since Version 7, which was generally available in March, 2001. Then, in Db2 Version 8 (GA in March, 2004), Db2's catalogs became Unicode and all SQL processing is conducted in Unicode, even if you're storing/retrieving EBCDIC data. It's the EBCDIC that "uses cycles," not the Unicode (UTF-8 or UTF-16, as you prefer); it's the EBCDIC that's "alien." And not really "alien," because it's all just so wonderfully and smoothly optimized now (and long ago). If you're using EBCDIC tables in Db2, they still obviously work. Yes, the EBCDIC data is getting converted back and forth *all* *the* *time* in the trip(s) through Unicode Db2, but "who cares." Let's not perpetuate mythologies, especially ancient ones. :-) -------------------------------------------------------------------------------------------------------- Timothy Sipples IT Architect Executive, Industry Solutions, IBM Z & LinuxONE -------------------------------------------------------------------------------------------------------- E-Mail: sipp...@sg.ibm.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
