Error handling

jeet_81 · Post by **jeet_81** » Fri Nov 11, 2011 3:14 am

Hi All,

I am developing a sequence job which has got 5 job activities which calls 5 different parallel jobs. Now is there any way to capture the errors/warnings for the 5 different jobs in the sequencer job so that I can build my error message and throw it.

Hope I have made it clear what is the requirement.

chulett · Post by **chulett** » Fri Nov 11, 2011 7:05 am

You would need to create a custom routine to go get whatever error messages you wanted from the logs of the jobs the sequence ran. Up to you then how you "throw" it after that. If you don't need the details but just the high-level list of what failed, that would be in the log of the sequence itself.

fmou · Post by **fmou** » Sat Nov 12, 2011 11:00 am

You would need to create a custom routine to go get whatever error messages you wanted from the logs of the jobs the sequence ran.

That's kind of expensive.

No wonder in our place, no matter how many jobs you can run in parallel, when put into a job sequence, we don't let then run in parallel but sequentially. Is that the actual reason?

Let me ask this way,

I need my 5 job activities which calls 5 different parallel jobs to run in parallel, wait until they all finish, then start next group of concurrent parallel jobs if all finished OK, otherwise abort the job sequence.

It is possible?

Thanks

chulett · Post by **chulett** » Sat Nov 12, 2011 11:29 am

That's a completely different question.

Have you tried putting the five Job Activity stages in the Sequence with no dependancies between them? Run them to a Sequencer set to 'All' with their trigger expressions set to 'Ran OK' and the next set of Job Activities would only run after all five had completed successfully. Lather, rinse, repeat for the next group.

An 'Otherwise' trigger from each could handle the error path, perhaps even using another Sequencer set to 'Any' to act as a funnel.