Page 1 of 1
Posted: Wed Mar 05, 2008 5:53 am
by ray.wurlod
The site where I am currently working uses UTF-8 almost exclusively, using Oracle databases. There are a couple of exceptions where external providers send text files encoded using Shift-JIS. DataStage copes perfectly well with both.
The only mapping error I've encountered is a Japanese hyphen character in a text file that was otherwise ASCII.
Posted: Wed Mar 05, 2008 6:02 am
by PhilHibbs
ray.wurlod wrote:The site where I am currently working uses UTF-8 almost exclusively...
And can you load DataStage-produced UTF8 files into Excel?
Posted: Wed Mar 05, 2008 6:22 am
by ray.wurlod
Yes. But not directly because - being in Japan - Excel is set up to expect Shift-JIS. But you can specify different map if you open a worksheet then use the Import Data\Import External Data menu option (under Data menu, from memory). I think the field is called "File Origin" or something similar.
Posted: Fri Mar 07, 2008 9:35 am
by Eric
Have you set the code page in the job design, not the OS where the DataStage Engine lives?
What stage are you using?
Re: UTF8
Posted: Fri Mar 07, 2008 9:59 am
by chulett
PhilHibbs wrote:Additional info: or should that be, WTF8?
Sorry, just noticed this and had to laugh.
Whew, better now.