RE: Moving bytes from a SBCS EBCDIC field to a DBCS Unicode fieldwithout translation

I think I wouldn't get EBCDIC involved in the mix.  I'm not sure what
populates your "from" field (the one that's currently EBCDIC), but maybe you
could just pass it either the address of the Unicode field, or maybe an
array of 3u0 (byte) elements.  My point is that whatever is building the
"from" field isn't really building an EBCDIC field, it's building Unicode
data, so you really shouldn't have an EBCDIC field in the mix.

Another option might be to change the code page of your program to 65535.
That should forestall any translation.

Joe


> From: James H H Lampert
>
> 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?