|
Thanks Bruce. I'm not sure how to find what codepage that I'm using. Is there a command or api that I need to use to find this info in AS400 or RS6000? -----Original Message----- From: Bruce Vining [mailto:bvining@xxxxxxxxxx] Sent: Thursday, February 05, 2004 9:56 AM To: Midrange Systems Technical Discussion Subject: RE: ASCIIi to EBCDIC There is really no way for us to answer your question with the information available. Your system might be running in a variety of codepages and only you can know which one you are using. For instance there are many locales available based on ISO "ASCII" standards. If we look at "ASCII" x'F0' for the following ASCII code pages we find that the character used is: Code page 813 x'F0' is Greek small letter pi Code page 819 x'F0' is Latin small letter eth Code page 912 x'F0' is Latin small letter d with stroke Code page 915 x'F0' is Cyrillic numero sign Which character do you "want" for x'F0'? On PCs running Windows there are similiar considerations. Again using x'F0': Code page 1250 x'F0' is Latin small letter d with stroke Code page 1251 x'F0' is Cyrillic small letter er Code page 1252 x'F0' is Latin small letter eth Code page 1257 x'F0' is Latin small letter s with caron and going further back in time Code page 850 x'F0' is soft hyphen. All of the above are "ASCII" and as you can see all are quite different. For your target code page/CCSID the same questions apply as EBCDIC has similiar considerations. For instance pi is available in CCSID 423 (at x'AD') and Cyrillic numero in CCSID 880 (at x'58') but neither exist in CCSID 37 (though small letter eth does at x'8C'). And of course both systems could use UTF-8 (which is sometimes viewed as an "ASCII" encoding) which would allow all of the above to be used... Bruce
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.