DSXchange

Maybe, but DataStage (in server jobs) does not enforce things like maximum length for VarChar, so it doesn't bite till you get to the INSERT/UPDATE statement.

Plan to phase out Version Control. It does not exist in Version 8.0, and will not be incorporated in future releases. Instead some means of integrating with "regular" SCCS tools, like ClearCase, will be implemented, possibly in version 8.2.

... but not quite so relevant outside the USA.

Thank you for the thought.

That it's here will mean that DSXchange will forward it to IBM. If you wish, you can also raise a formal enhancement request through your support provider.

Are the data pre-sorted when they are written to the Data Sets? If so, include an explicit Sort stage ahead of the Aggregator, and specifically make the sort rule for the key columns "Don't Sort (Previously Sorted)". This will prevent DataStage from inserting tsort operators. View the score to see t...

Only the error message permits cogent diagnosis.

Sorry, I was a bit terse. I meant, given that the question is about changing IP address, why did you give an unqualified answer about changing the machine name?

What has changed? "Nothing" is not the correct answer.

Example: your column is Char(12) and your data length is greater than 12.
Example: your column is Number(7) and your data value contains more than 7 digits.

Char(0) is not NULL, it is NUL. It is a valid character from Control Set 0. NULL is "the value that means unknown" and is different in different databases. Internally in DataStage it is represented using Char(128). When reading/writing sequential files you specify how NULL is represented. Len(Char(0...

ArndW wrote:DataStage itself would need to be reinstalled only when changing the machine name.

Why?

And if only the IP address is changed, even that ought to be unnecessary.

The Operator role can only run RELEASED jobs. It's a major restriction, which is why hardly anyone makes use of that role, and why IBM has put in the SuperOperator role in version 8.0.

And sometimes you do it without explicitly progamming it. DSExecute() uses this technique to capture the output, as do the before/after subroutines ExecSH, ExecDOS and ExecUV.

That's the idea, provided that the data types match.

That's very odd; DataStage itself does not use Select List #10. Are you sure it wasn't Select List #0?