DSXchange

The difference as compared to what? :? A 'Row Merger' simply takes all of the incoming fields and 'merges' them into a single column / field. Is that what you are trying to accomplish? As requested, can you state your full requirements for the job in question - what is it meant to do? Perhaps the Ro...

Welcome. Correct, hashed file records are uniquely identified by their key value and duplicates are handled in a destructive overwrite or 'last one in wins' manner. Hard-coding a key like that works when you only have one record in the hashed file that you need to look up over and over. How do you n...

We are not sure what you meant by exactly "Terminators in the final column must be Quoted".Is that something the actual data in Description column should be quoted? Yes, that is what I meant and that is what allows the stage to differentiate between termintors "in the data" and ...

DataStage on UNIX uses 'sendmail' under the covers and that only supports HTML if the message is MIME encoded. For one example, see here. Which also means you'll need to roll your own email routine to accomplish this, unless (perhaps?) you send the HTML document as an attachment instead of in the bo...

Yah, not a query... and a better question for your DBA than us.

Well... first off this isn't your topic and thus not your data, only the data that you've created in what you assume is a match for the original poster's data. Secondly, have you validated what you have as the 'terminator' inside that last field? Perhaps you should only be converting one of the two ...

Or a flaw in your understanding.

Terminators in the final column must be Quoted to be recognized as data, meaning inside the quoted string that is the final column's data.

This would be trivial in a Server routine.

The same way. However, it's unclear from your post if you tried repeating the Convert for the Description field as well... did you?

Hmmm... we used DataStage 7.x on Citrix back in the day. One thing to note, however, is it was just for the client software and we never had any issues with it.

As a guess, perhaps your quotes are being stripped out.

I recall issues with embedded quotes but thought there was some sort of equivalent for this in the PX Sequential File stage, guess I thunk wrong. For those of you who have faced and overcome this issue, what solution did you architect? What was your 'work around'? Ah... I see Ray added his while I w...

Ray is being pedantic again.

Then how about just "the equivalent" rather than "the equivalent property"... as in how would one handle the situation in PX.

Is there any attribute of this 'dummy' row that uniquely identifies it? If so, you could filter on that.