Unlinked stages in one job

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
aaryabhatta
Premium Member
Premium Member
Posts: 20
Joined: Mon Dec 19, 2005 10:00 pm
Location: UK

Unlinked stages in one job

Post by aaryabhatta »

Can somebody help me understanding the process flow of a job when there are different inputs and write to the separate stages unlinked?
Like
dataset --> Oracle stage
dataset --> Oracle Stage
dataset --> Oracle stage all in the same job

Will all the inputs start processing at the same time sharing the nodes? How is it different from having three differnt jobs? Is there any advantage of jobs developed in this manner?

Thanks in Advance!

Regards
nagarjuna
Premium Member
Premium Member
Posts: 533
Joined: Fri Jun 27, 2008 9:11 pm
Location: Chicago

Post by nagarjuna »

All these will start at the same time.Depending on the requirement If you want more control then go for a sequence .
Nag
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

As noted, they will all start at approximately the same time and run as if they were three separate jobs. However, a failure in one job stream could doom all of the others, depending on the timing. It could also complicate restarts.

No advantage, really, that I can think of. I'll guess that the thought was 'one job rather than three' (since three jobs must be evil) but to me it's just... lazy. :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply