DSXchange

What is not working?
Place your path and the shell name in the 'Command' option and Parameters in the available Parameters option.

You can find the list of product classified under IBM's website.
http://ibm.ascential.com/products/

What is the datatype for ADDR_KEY in datastage?

If you dont have any change in the metadata or with some configurable change, you can approach the suggested options. If the metadata is different from present, you need to go for different jobs.

Check the director log for the exact command that been executed from Datastage.

Try to create a copy of the same job and remove most of the stages, and try to run the report. This is to make sure that, the error is due the large stage Numbers.
BTW: Does you job works withou any issue like resource contraint or intermetten cutoff problem with this 100 stages.

What was the load on the server during when you get this error. Try to monitor the CPU and Memory usase while you run this job. Try to change the temp directory from /tmp to some other directory. There are chances where /tmp will be aloted with more space and might be moved into a spereate mount. Th...

If the whole point of not spliting the job is to not land the data in between, then you very well use the highlight of PX, Persistent dataset. Which will alow you avoid IO to a very great extend when compared to Sequential file. You cannot have hard and fast rules for the number of stages, but it is...

Hope this was your initial requirement, to update Null values and not to update the Not null values.

Could see Arnd's post in the same regards.

Will the same persiste in different PC as well?

If you are sure, that both input and output are of same datatype and same lenght in the given stage, check for RPC. If that is enabled, disable it.

Hope OP reply to this issue. Can you explain what is not working?

Waht is the datalentgh, sqltype, Nullability for the 'ID' field in LKP_ID stage?

What is not working? What column you are expecting to be updated? Under which condition?