Job Sequence question

[srini]

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

[iwin]

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

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.

[Krazykoolrohit]

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:-)

[DSguru2B]

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.

[sri1dhar]

Don't forget to check the "Automatically hanle activities that fail" option in the General job properties when using a Exception handler.

[ray.wurlod]

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.

[Krazykoolrohit]

can i abort the sequence in this way if a job aborts?

I have one routine and a job notification stage, which i want to run when a job fails.

Job1-Notify(fail)

Exception handler - notify(seq fail)

If i handle the error in the job, exceptional handler doesnt capture it

[Krazykoolrohit]

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?

[DSguru2B]

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.

[Krazykoolrohit]

I have around 20 jobs in one sequence. It looks rather clumsy connecting all of them to one.

this is the way its currently designed. I was looking into the possibility of another design to improove the legibility of the sequence

[chulett]

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?

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]

is there nothing in pallete that can help me?

something which transfers the loop to the job next in sequence?

[kumar_s]

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.