As I recall from experiments I conducted some months ago, when I try to move data from a character (SBCS EBCDIC) field to a graphic (DBCS Unicode) field in RPG (the actual bytes are already DBCS Unicode), the RPG runtime assumes the source data is EBCDIC, and garbles it by forcibly translating it and/or inserting SI/SO control characters.
My experiments never got far enough to find a way to avoid 
this translation. Is there an easy way?
Would it be as simple as overlaying (e.g., as a coincident 
field in a data structure) a Unicode field on the source 
field, and using the Unicode overlay in the MOVE/MOVEL 
statement? Or is there a different approach that's better?
--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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 copyright@midrange.com.

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.