Reg. Restartability of the DataStage job Sequencer
Posted: Mon Jul 10, 2006 2:48 pm
We are trying to kick of three different jobs(Job Sequencers) parallaly with the help of a Job Sequencer. There are two Sequence Job activities one with ANY and other with ALL types and two notification activities which sends mails upon success or failure of any three activities.
Here we are supposed to use the DataStage Restartability. Whenever a job fails, failure notification activity is sending an email and the main sequencer is taking the success status of that Notification activity as it is the last activity of that sequencer.As a result we are loosing the Restartability.
In order to avoid this case, i used the Abort activity to set the Main Sequencer status Abort, as the sequencer is in abort stage i was able to restart the job Sequecer where it left off.( This logic was working fine when my jobs are running sequentially one after other and am able to use the DataStage restartability).
Abort activity is sending stop requests to all the other jobs that were running when ever one of my three jobs(running simultaneously) failed.
1. I want the remaining jobs to be completed with out any interruption and report the main sequencer that they are successful.
2. The status of the main sequencer to be Abort so that i can restart the job that was aborted.
I used all the options that the Abort activity has, jobs are getting SigInts(Stop requests) and getting aborted.
Can you please share your ideas.
Thank You
Srinivas
Here we are supposed to use the DataStage Restartability. Whenever a job fails, failure notification activity is sending an email and the main sequencer is taking the success status of that Notification activity as it is the last activity of that sequencer.As a result we are loosing the Restartability.
In order to avoid this case, i used the Abort activity to set the Main Sequencer status Abort, as the sequencer is in abort stage i was able to restart the job Sequecer where it left off.( This logic was working fine when my jobs are running sequentially one after other and am able to use the DataStage restartability).
Abort activity is sending stop requests to all the other jobs that were running when ever one of my three jobs(running simultaneously) failed.
1. I want the remaining jobs to be completed with out any interruption and report the main sequencer that they are successful.
2. The status of the main sequencer to be Abort so that i can restart the job that was aborted.
I used all the options that the Abort activity has, jobs are getting SigInts(Stop requests) and getting aborted.
Can you please share your ideas.
Thank You
Srinivas