CCSID value

ml · Post by ml » Wed Jul 20, 2005 6:47 pm

Hi, i'm getting this warning message in one ODBC reference:
TRANSLATION FROM CCSID 1252 TO 937 NOT DEFINED

any help will be appreciated.

thanks,

ArndW · Post by **ArndW** » Thu Jul 21, 2005 12:35 am

ml,

the CCSID doesn't ring a bell, but the 1252 and 937 are codesets (1252 is Windows Latin codepages, and 937 is traditional Chinese).

Do you have NLS enabled in DataStage or in the database?

chulett · Post by **chulett** » Thu Jul 21, 2005 6:56 am

Threw the whole phrase into Google and quite a bit came up. Seems to be related to AS/400 platforms and DB2/UDB databases. CCSID stands for 'Coded Character Set Identifier', btw, so I think you are on the right track Arnd.

ray.wurlod · Post by **ray.wurlod** » Thu Jul 21, 2005 4:56 pm

Could that be a DETLA (doubly extended three letter acronym)?

ml · Post by ml » Wed Jul 27, 2005 8:44 am

ok, we have NLS installed and I know that this db2 reference is an as400 server in china, so i asume that has a chinese char set 937... but now what should i change to eliminate this warning?

thanks

ArndW · Post by **ArndW** » Wed Jul 27, 2005 8:47 am

mat,

is this a problem with the table as a whole or with a specific value in a row? In the first case you will need to set the NLS for the job as a whole and in the latter it might mean that a character has shown up in the table which cannot be mapped into the target character set.

So, where and how does this error occur?

ml · Post by ml » Mon Aug 22, 2005 2:32 pm

This warning appear in a whole column mapped in a direct reference. I solve the problem when I put a hash file in the middle. But this is not the solution I want... any idea on how to solve this issue?
this is the detail:

Code: Select all

        Reference (China code page CCSID 937)
                |
Input value--->TRF--->Output value
(Latin CCSID)

warning message "TRANSLATION FROM CCSID 1252 TO 937 NOT DEFINED"

Where should be this translation defined?

thanks,

ps: another solution I found is change the code page in the database for this table, but again is not the best solution...

ray.wurlod · Post by **ray.wurlod** » Mon Aug 22, 2005 5:54 pm

How about telling us what solution you DO want?

ml · Post by ml » Mon Aug 22, 2005 10:20 pm

Ray this warning started after an ODBC driver upgrade. The solutions I found are possibles, but implicate a lot of coding modifications.

So, I think that it should be another option like add a char set in the odbc.ini or use another NLS in the odbc stages. I tried both, but no luck yet.

Thanks,