DSXchange

Hi,
I was hoping someone roaming this forum may give me some direction on this. We are running DatasStage 9.1.2 on Windows with NLS enabled. When I check the installed Charactersets in NLS in the Administrator Client I see the Characterset ISO8859-15 as installed. When I run the command iconv -l it returns some charactersets but not the full list of those shown in administrator and not the one we are looking for (ISO8859-15 ).

Just figured I would take a chance asking here since I have always received great responses in the past to my DataStage questions.

Thanks and Happy Holidays! John

That is possible, since the MKS-Toolkit "iconv" command is different from what is shown inside DataStage. Is there an issue with using the ISO8895-15 character set in your jobs?

The developers have not tried that as they are waiting for me to guide them. If the project is defaulted to another Character-set could we still use the Iconv with the ISO8895-15 character set?
Would you happen to know if this can be used when the input is an XML file?
Thanks - - John

what happens if you try something like from the command line? Does it work or give an error?

I receive the following from the command line:


D:\JohnP>SH
$ iconv -f iso-8859-15 -t utf-8 00201720100318011426.xml
iconv: Invalid codeset: utf-8: The system cannot find the file specified.
iconv: Invalid codeset: iso-8859-15: The system cannot find the file specified.

I'm not at a Windows (or a v9) system, but according to the MKS documentation I found there should be LC_... files in the directory "/etc/iconv". There are only 8 character mapping differences between 8895-15 and 8895-1, so you could copy the file(s) and make those changes manually.