I just wanted to thank everyone for their input, no wonder I couldn't find any easy solutions, I didn't realize what a large "can of worms" I had opened, not realizing that I needed a whole "service", not just a routine.
I will take everyone's input and try and decide on the ultimate solution that will work for me. At this point I am told by customers that all I need to worry about (for the near/medium future) is just a subset of the extended Latin-1 character set. It is really just the accented vowels and consonants that I'm told I need to deal with. Not sure yet if I can use this assumption to utilize a simpler solution rather than supporting the entire UTF-8 character set, which I now understand is...HUGE. Thanks again to everyone who replied with suggestions and help in understanding what I'm facing here. John -----Original Message----- From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On Behalf Of Bob Cronin Sent: Tuesday, November 20, 2012 10:46 AM To: [email protected] Subject: Re: CMS-PIPELINES Digest - 1 Nov 2012 to 19 Nov 2012 (#2012-22) Of course its simpler if you know you're always dealing with latin-1. -- bc On Tue, Nov 20, 2012 at 12:56 PM, Glenn Knickerbocker <[email protected]>wrote: > On 11/20/2012 11:04 AM, Bob Cronin wrote: > > I used to have my own Rexx code to > > translate utf8 to utf16, but dropped that in favor of the "undocumented" > > utf stage the Piper was so kind to provide. So basically you just need to > > convert utf8 to utf16 and then use the Unicode to EBCDIC table > appropriate > > to your situation. > > I think by "ASCII UTF-8" he really means UTF-8 encoded 8-bit Latin-1 > (ISO 8859-1), so VCHAR should fill in the missing step by skipping over > the extra 8 0-bits. From EBCDIC to UTF-8: > > ... | utf from utf-8 to utf-16 | vchar 16 8 | xlate a2e | ... > > From UTF-8 to EBCDIC: > > ... | xlate e2a | vchar 8 16 | utf from utf-16 to utf-8 | ... > > ¬R >
