|
hi Brad,
RPG has a rather weird default. It doesn't use the job's CCSID by
default, instead it uses the mixed-byte CCSID that's related to the job
CCSID.
So if your job is CCSID 37, RPG will use 937. 937 fully supports CCSID
37, but will treat the x'0e' and x'0f' as "shift-in" and "shift-out"
characters, allowing it to also process Chinese symbols.
You can override this default behavior by specifying
CCSID(*CHAR:*JOBRUN) on the H-spec.
On 10/31/2011 1:27 PM, Bradley Stone wrote:
Actually I found the issue here, and it wasn't the APIs... I was--
doing some other conversions on it and doing a %CHAR on the variable
and THAT is what was messing it up... I'm still trying to remember
why I was doing that. :)
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
