I think source itself might convert - but programs created from source
that has character literals - those won't convert the literals - they
end up using the code point pulled in at compile time. Hence, pipe turns
But this is why the at-sign and dollar-sign probably should not be used
in variable names in RPG - at least, I think that's right. There goes
all that naming of subroutines with the dollar sign at the beginning of
I hope I'm wrong on that!
Eschew variant characters in source!!
See you in a couple!
On 8/30/2012 3:55 PM, David Gibbs wrote:
On 8/30/2012 3:09 PM, sjl wrote:
I have several RPG programs which are being deployed via Implementer to
It's been a while since I've looked at that code but, as long as the source physical files have the correct CCSID, the contents of the source should be trans-coded correctly.
several different LPAR's being used by different world areas, one of which
is for Europe.
The source files are all defined with CCSID(37), but the European
environment is using CCSID(500).
How do I deal with the variant character | (the pipe symbol) across these
In CCSID(37) , the pipe symbol is X'4F', but in CCSID(500) the pipe symbol
We have a number of customers that use Implementer to deploy code to machines running different CCSID's.
If you have any specific problems, please contact PTC Integrity (formerly MKS) support at integritysupport@xxxxxxx.
(who works for PTC Integrity on Implementer in addition to running these lists).