DSXchange

Murali,

The special characters will be created due to incorrect mode of data transfer across platforms. Try toggling the transfer mode to ASCII or Binary. See if this resolves the issue.

--Tony

Let's take this from step 1. Are these characters legal ones for the text strings you are reading from DB2 or not; i.e. are you reading and transferring them correctly to DataStage (ignore XML for the moment)?

Right, take XML out of the picture for the moment. What is the characterset of your source and target? Do you have NLS installed?

ps. Moved to the proper forum.

Thanks for inputs guys,

Yes Arnd. these are legal strings from DB2. I could query through the tables and looked the data, its looking fine.

Craig,
NLS are installed properly and by defaul it has been mapped to UTF 8.

But The next step when i do for generating xml dynamically, it results in an extra special character appended the Pound sign.

Take a look at the encoding that you are using....there was a thread in here a week or so ago where we were talking about the copyright symbol. In there I posted the results of some research with the various encodings. That might help.

Worst case, you'll need to convert it an put in its escaped hex value (hints also in that thread, if you can find it).

Ernie

Thanks Ernie. I tried the character code and hex code earlier and resulting unsuccessful. As i told in the earlier posts i'm dynamically generating the XML's.When i pass the hex code to the appropriate db2 column. I'm getting the the hex code as &hexcode. Can you have some other way to parse it and place the code into the concerned field.

<Murali>

What's wrong with the &amp hexcode? Any tool reading the xml should work fine with that too.

Lots of info out there on this, for example here. Scroll down to the 5. References section in particular the Character Predeclared Entity bit.