Everyone should be coding the CCSID(*CHAR) keyword
barbara_morris 120000DX5W Comments (2) Visits (5009)
Strange but true: By default, RPG assumes that the CCSID of alphanumeric data is the mixed double-byte + single-byte CCSID that is related to the job CCSID.
This matters when all of the following conditions are met
If this data is being converted to Unicode, and the data is not really supposed to be interpreted as mixed-byte data, then the Unicode version of the data will not be correct.
If you are actually using a mixed JOB CCSID, nothing will change. If you are actually using a single byte CCSID, any conversions involving alphanumeric data containing x'0E' will be correct.
But I never have x'0E' in my single byte alphanumeric data
Well, hardly ever ...