DSXchange

Just add them like you would any other UNIX user - because they are. Just make sure the group permissions are correct for DataStage.

Will I see an improvement if I change the array size to 100 and the transaction size to 10000. Probably. Change it and let us know. Also would this mean my reject will not be captured properly ?? If you were using Oracle, the answer would be an emphatic YES with any array size greater than one. You...

Good. :D

For the record, I didn't say to grep the bad file, merely checking for its existence is enough. I have been known to grep the actual 'log' file for specific errors as well as check the return code explicitly.

Data in but not out of that stage would imply your XPath Expressions couldn't be matched back to the XML. How about posting them?

If you really think you need to take this approach, read the multiserv.pdf document in your Docs directory. It explains all that is involved.

Yes, you can - but are you sure you need to? What does 'module' mean in your world? Can you not just create a new Project (or Projects) for this?

Define the first 90 columns and enable the 'Ignore truncation warnings' option.

All it takes is a trailing space (for example) for one field to not equal another, something we can't tell from here. What is the dash supposed to represent? All it takes to 'update' a hashed file is to do exactly what you are doing - send the complete / replacement records in again. As long as you ...

No such thing as duplicate keys in a hashed file. Honest. You need to check your data / process a little closer it seems to me.

Use the Wait For File stage or just script the polling yourself.

How can you not know what variable to change? How can you expect us to know?

Just change the value associated with it in the Administrator... it is defined there, is it not?

Use 'sh' or 'ksh' as the Command and then put the entire parameterized command itself in the Parameters box.

You need to mark the 'lowest' element as the repetition key - try your 'Value' tag.

Hmmm... I vaguely recall 'hard coding' the schemaLocation in the stage at design time once - in the Namespace Declaration tab. But that meant I stashed a copy of the xsd it validated against in the location I specified.

Pretty sure it worked...

Which 'primary key tag'? Try moving it lower, like whatever 'D' is.