On one platform we see that when we CAST an input message BLOB to CHARACTER (where the CCSID of the message is 819) we get the ASCII equivalent of the BLOB.
On the other platform we see that our ASCII characters have additional UTF-8 characters inserted where the ASCII character value is above 0x7F (as per the UTF-8 standard).
As example would be and input message:
0xa33530
on one system the CHARACTER cast give us...
"£50"
But on the other system we get...
"£50"
Note we see that the "Local" (region) settings on the sun platforms differ, and infact on the platform where the unwanted UTF-8 encoding is being applied the platform is complaining -> "couldn't set locale correctly".
Note although I do not realy understand these SunOS settings our errant UTF-8 machine has the following.
The problem occurs on the Production machine (GB local), but does not on the UAT machine (US local). We are not allowed to touch either at the moment, although the Production machine will be retired soon.
We did notice that the Production machne has the environment variable
LANG=en_US
Operations changed this to en_GB and we are no longer getting our "couldn't set locale correctly" message any more. We of course do not know if we have still have the UTF-8 problem.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum