Job Sequence question
Moderators: chulett, rschirm, roy
Job Sequence question
I have 4 jobs which run in parallel in Sequence. I want to be notified through email ONLY if any one of the job aborts. How do I do that???
I understand I have to use Notification Activity stage but can somebody throw some light on the design aspects like how many Notification stage I should use and how to send a job status mail only if the job fails etc
Also could I accomplish the same thing by using a scripts
Thanks in advance for your help
Srini
I understand I have to use Notification Activity stage but can somebody throw some light on the design aspects like how many Notification stage I should use and how to send a job status mail only if the job fails etc
Also could I accomplish the same thing by using a scripts
Thanks in advance for your help
Srini
Re: Job Sequence question
Well, if you have 4 jobs running in parallel then u can link all those to a sequencer stage with tigger set to failed and in the sequencer stage u have to set the mode to any and then followed by one notification activity.srini wrote:I have 4 jobs which run in parallel in Sequence. I want to be notified through email ONLY if any one of the job aborts. How do I do that???
I understand I have to use Notification Activity stage but can somebody throw some light on the design aspects like how many Notification stage I should use and how to send a job status mail only if the job fails etc
Also could I accomplish the same thing by using a scripts
Thanks in advance for your help
Srini
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
link all the 4 to a sequencer stage and change the mode of the stage to "any". link the sequencer stage to "notification activity" stage and fill in the details
In each of the 4 jobs(in sequencer), in triggers tab, change expression type to FAILED (conditional)
Job 1 -> sequencer1
Job 2 -> sequencer1
Job 3 -> sequencer1
Job 4 -> sequencer1
sequencer1 -> notification activity
and you would be good to go:-)
In each of the 4 jobs(in sequencer), in triggers tab, change expression type to FAILED (conditional)
Job 1 -> sequencer1
Job 2 -> sequencer1
Job 3 -> sequencer1
Job 4 -> sequencer1
sequencer1 -> notification activity
and you would be good to go:-)
If you have the exception handler stage then no need to connect all of them to a sequencer with mode 'Any' and then to the notification activity.
Just drop an exception handler connected to a notification activity. When any job fails, the control will be passed on to the exception handler which in turn will trigger the notification activity.
In other words, avoid the spider web.
Just drop an exception handler connected to a notification activity. When any job fails, the control will be passed on to the exception handler which in turn will trigger the notification activity.
In other words, avoid the spider web.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Unless, of course, you want separate messages from each of the jobs. IN that case, each job requires its own "lack of success" trigger to its own Notification activity (and maybe a Routine activity as well to invoke UtilityWarnToLog).
Tigger should only be used when you want something bounced.
Tigger should only be used when you want something bounced.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
i changed the job design to
job1 - Job 2
Exception handler - notify (sequence) - Notify (job fail)
and its working
The issue now is when i say that job2 should run after job1 unconditionally and job1 fails, i want the control to pass to job2. ofcourse i need the exceptional handler to work too for job1?
job1 - Job 2
Exception handler - notify (sequence) - Notify (job fail)
and its working
The issue now is when i say that job2 should run after job1 unconditionally and job1 fails, i want the control to pass to job2. ofcourse i need the exceptional handler to work too for job1?
Connect the exception handler to a sequencer with Mode set to 'any' going to your second job. The sequencer will also have another input coming in from the sequencer. This way job 2 will be fired even though the control is passed to the exception handler.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
If I'm understanding your need, you are out of luck - you can't have it both ways. Either you are handling job failures via links and triggers or the Exception Handler is handling them. And once the Exception Handler kicks in, control transfers to that part of the process. In other words, at that point you are done.Krazykoolrohit wrote:The issue now is when i say that job2 should run after job1 unconditionally and job1 fails, i want the control to pass to job2. ofcourse i need the exceptional handler to work too for job1?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
Or have a routine to send mail regarding the status of each job in AferJobSubroutine.
Anyway by having the unconditional trigger of each job, you dont have to abort the sequence untill all finishes. So the same routine in after the sequence gets over.
Anyway by having the unconditional trigger of each job, you dont have to abort the sequence untill all finishes. So the same routine in after the sequence gets over.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'