Re: Hex translation

Åke

This sounds like the system is doing what it should. I don't think tables are used for this implicit conversion. Something like iconv is used under the covers, as I think you know - you live in an environment that needs multiple encoding more than we do.

Still, I did find table Q037959870 - this goes from 37 to 870 and maps x69 to x72. And Q870697037 maps the opposite direction. This is on a V5R1 machine, so they've been around awhile. I don't know if they are round-trip conversions, but maybe they are.

HTH
Vern

On 2/21/2012 4:39 AM, Åke Olsson wrote:

We have the following:

A Physical file (customer file) which has CCSID = 37

A user (in Poland) which has CCSID = 870 and a client-access host code page also set as 870.

What we see is that a specific character in a name field is stored as X'69' in the database but when the user program retrieves it is translated to X'72'.

Same thing other way - when the user writes a X'72' character it is stored in the database as X'69'


In many ways this makes sense the char the user sees and keys is a capital "E" with some accents underneath.

What is slightly frustrating is that I cannot find a table that describes the rules for the translation. Is there one anywhere? I would need something along the lines:

CCSID-37 hex code translated to CCSID-870 hex code



Med vänlig hälsning / Best regards

Åke H Olsson
[Description: cid:image001.png@01CA1FE6.387A03A0]
Box 433 SE 551 16 Jönköping Sweden visit: Brunnsgatan 11
phone: +46 (0)36 342976 mobile: +46 (0)705 482976 fax: +46 (0)36 34 29 29
ake.olsson@xxxxxx<mailto:ake.olsson@xxxxxx> www.pdb.se