Sequencer Abort jobs after warnings setting

ramnishgupta · Post by **ramnishgupta** » Fri Jan 16, 2009 1:59 pm

I have a sequencer that calls multiple jobs under it. When I launch the sequencer using a shell script I pass it the Warning limit of 50. However this limit is not charring forward to the underling ETL jobs.

Is there a way in which we can pass down the warning limits to the job level when launching the sequencer?

Thanks

chulett · Post by **chulett** » Fri Jan 16, 2009 2:06 pm

Hmmm... that should be happening automatically. The only time I've seen that not happen is when people were not using a Job Activity stage to run their jobs. How are you running yours and what warning limit do they end up using?