× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



David,

You are assuming that there is one and only one "correct" DBCS CCSID given a SBCS CCSID. Unfortunately this assumption is not a safe one. Change "correct" to "a" and you're on safer ground :)

If we look at Japanese and the DBCS CCSIDs that utilize the SBCS CCSID 1027 then you will find that both CCSID 5035 and CCSID 939 meet that requirement. Which is "correct"? I couldn't say without more information. Both use the same code pages, but 939 supports the larger character set.

If we expand the search to include those DBCS CCSIDs that utilize the 1027 code page (rather than the 1027 CCSID as that CCSID does not utilize the full range of assignable code points) then you will also find that CCSID 1399 now qualifies. As this CCSID, based on SBCS CCSID 5123 - code page 1027 and a growing character set, includes the euro it may well be "correct" in some scenarios also.

There are APIs to provide related/associated CCSIDs, but this does not mean that the returned CCSID is the only (or even best) CCSID possible.

Bruce Vining


David Gibbs <david@xxxxxxxxxxxx> wrote:
David Gibbs wrote:
Anyone know if there is a way to determine the correct double byte
CCSID based on a single byte CCSID?

Hmmm ... looks like CDRGRDC, passing an encoding scheme of x'1301', might do what I want (http://publib.boulder.ibm.com/iseries/v5r2/ic2924/info/apis/CDRGRDC.htm)

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.