Re: UNICODE application on IBM Mainframe
I would like to add one item to this discussion: Recently, someone from the IBM S/390 group told me that they had decided to store and use Unicode on S/390 as UTF-8/16/32. They will not use UTF-EBCDIC. I am not aware of anyone inside or outside of IBM who does use UTF-EBCDIC. (There is another EBCDIC-friendly proposal out there in IBM that also does not seem to have been adopted.) If the IMS DB is now updated to use Unicode, then it is probably as UTF-16, right? markus
Re: UNICODE application on IBM Mainframe
The IMS DB supports UTF-16. Actually, you can store anything you want in an IMS DB - if you want to provide all your own transaction management. IMS provides transaction management for UTF-16, just not through any 3270-based applications. Lisa Markus Scherer [EMAIL PROTECTED] on 01/23/2001 10:18:35 AM To: "Unicode List" [EMAIL PROTECTED] cc: Subject: Re: UNICODE application on IBM Mainframe I would like to add one item to this discussion: Recently, someone from the IBM S/390 group told me that they had decided to store and use Unicode on S/390 as UTF-8/16/32. They will not use UTF-EBCDIC. I am not aware of anyone inside or outside of IBM who does use UTF-EBCDIC. (There is another EBCDIC-friendly proposal out there in IBM that also does not seem to have been adopted.) If the IMS DB is now updated to use Unicode, then it is probably as UTF-16, right? markus
UNICODE application on IBM Mainframe
I am investigating using the Unicode standard to store and forward Chinese characters in a mainframe (IMS) environment. Basically we want to receive Chinese into the system, encode into UNICODE, send it to the mainframe and store on the IMSDB. At a later stage, then decode back into Chinese for forwarding out of the system. Any advice or feedback from anyone who has done anything similar would be appreciated. How would the unicode look stored in EBCDIC? for example, code point 006D for 'n' - stored as character '00D6' or hex x'006D'? What about the 'U' - or does one HAVE to use one of the UTFs? As you can tell, this is all still new to me. Any hints and tips would be appreciated as well as whether this is feasible or not. In future we would also want to store and forward other languages, as well as possibly update the values using a front- end interface. Regards, Tracey _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Re: UNICODE application on IBM Mainframe
Unicode is always serialized in a UTF: UTF-8, UTF-16*, or UTF-32*. The definition of each of these is invariant across systems: in UTF-8 an 'a' is always stored as 0x61. There is a special UTF for use on EBCDIC systems. Check out the technical reports and FAQs on www.unicode.org. Mark - Original Message - From: "tracey kelly" [EMAIL PROTECTED] To: "Unicode List" [EMAIL PROTECTED] Sent: Wednesday, January 17, 2001 06:30 Subject: UNICODE application on IBM Mainframe I am investigating using the Unicode standard to store and forward Chinese characters in a mainframe (IMS) environment. Basically we want to receive Chinese into the system, encode into UNICODE, send it to the mainframe and store on the IMSDB. At a later stage, then decode back into Chinese for forwarding out of the system. Any advice or feedback from anyone who has done anything similar would be appreciated. How would the unicode look stored in EBCDIC? for example, code point 006D for 'n' - stored as character '00D6' or hex x'006D'? What about the 'U' - or does one HAVE to use one of the UTFs? As you can tell, this is all still new to me. Any hints and tips would be appreciated as well as whether this is feasible or not. In future we would also want to store and forward other languages, as well as possibly update the values using a front- end interface. Regards, Tracey _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Re: UNICODE application on IBM Mainframe
Within the IMS database, any form of data can be stored. Beware, however, that certain parameters, such as the transaction name, must always be in EBCDIC. While the database itself can handle Unicode in any format, you have to be careful about how you work with that data - the IMS Transaction Manager cannot handle Unicode. No 3270-based product can work with Unicode unless it is in the UTF-EBCDIC format. IMS shipped support for Unicode in V7, October 2000, to support working with Unicode using Java and IMS Connect. Lisa