Job sequence taking longer than the individual jobs

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
antonyraj.deva
Premium Member
Premium Member
Posts: 138
Joined: Wed Jul 16, 2008 9:51 pm
Location: Kolkata

Job sequence taking longer than the individual jobs

Post by antonyraj.deva »

i am running a job sequence which contains 4 jobs. after every job successfully runs it is taking exactly 8 mins to initialize the next job. that means it is taking exactly 32 mins to run all the jobs in the sequence. whenever i am running individual jobs it is taking only 40-50 secs to run a job. But in the job sequence why it is taking that much time to run the four jobs.
TONY
ETL Manager
Infotrellis India

"Do what you can, with what you have, from where you are and to the best of your abilities."
kduke
Charter Member
Charter Member
Posts: 5227
Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:

Post by kduke »

Get row counts had a similar issue. You need to run jobs either in job control code or using a routine and take out the WaitForJob(). That way the follow up jobs run in the background.
Mamu Kim
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Moved thread and renamed subject to something more meaningful.

Me, I'd be curious what exactly "8 mins to initialize the next job" means and why that would be happening.
-craig

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