DSXchange

Sudharsanan,

There is no straightforward command or stage that can do what I tried to convey. It is a set of tasks on its own involving few steps and having more information of the requirement.

That is why I left it to be decoded by the reader.

Try making the tablename as a job parameter and include the '#' as part the of name there.

Maybe your network traffic is on its peak.

Are you running only one job or a sequencer / batch job when this pops up?

Maybe you are looking for real-time processing !!

Better leave it blank to check.

Or use @TIME

Also if you are using Win XP SP2, check for a patch from ASCL for this purpose.

You can do a pre-job script of 'type file2 >> file1' and use file1 as your source.

Check whether you are changing any key columns as part of update.

From DataStage Admin or universe shell or any other means by which you can talk to universe.

Best is to have this as a stand-alone job.

You still have not answered the question of whether you can run the same SQL successfully outside DataStage.

...assuming that you source produce rows in the same order every time.

Otherwise, you may have to either clear the rows from target or check in any other way.

Write the return value to a log and confirm it is what you think it is.