Handle Abort automatically.

[dsdoubt]

Hi,

Version 7.0.
There is no option in JobProperty to handle the aborted job. So if any of the Child JobSequence aborts, the main Job sequence does not getting aborted.
No Termitator stage as well.
May I know, how to abort the mail sequence. Right now Iam using a separate routine to abort by extending a extra link for Failed.
Not even Sequencer stage with "All" works.

[ray.wurlod]

One obvious option is to upgrade to 7.5, where you get all of the goodies whose absence you bemoan.

What precisely do you mean by "abort the mail sequence"? What's wrong with the method you've chosen (using a trigger to detect the failure)?

There's no difficulty (using such an approach) to have a warning written to a job sequence's own log (use a Routine activity invoking UtilityWarningToLog); this will be detected by the parent routine and so on to the top of the hierarchy of job sequences. The message logged might even contain pertinent diagnostic information. Just think of the possibilities!

[chulett]

So if any of the Child JobSequence aborts, the main Job sequence does not getting aborted.

That's true - because nothing went wrong in the main Sequence job. You need to detect the problem in the 'child' Sequence job, propogate it up the foodchain by logging something in the child Sequence job and then handling it accordingly in the main Sequence accordingly. Note that a Warning will do rather than killing it off with an Abort.

Or simply stop executing any further jobs in the main Sequence. In your version with no check-pointing, there's no reason to abort the main Sequence. It will just complicate your ability to restart because (as you noted) Sequence jobs are not 'Aborted/Restartable' in your version. So a simple failure or warning trigger would suffix - in the main Sequence job, that is.

No Termitator stage as well.

A convenience, not a requirement. You really want the enhanced version of the Exception Handler stage that an upgrade would bring. Besides, I think that is some kind of root vegetable stage.

May I know, how to abort the mail sequence. Right now Iam using a separate routine to abort by extending a extra link for Failed. Not even Sequencer stage with "All" works.

Why... that's exactly how you do it in your version - in the 'child' Sequence job. Or in either of them, if you really feel the need to kill off your main Sequence. Specifically, you extend a Failure or Warning link from any stage you want to play this game, send them all to a Sequencer stage set to Any (not 'All', 'Any') and from there link to your destructive device of choice. Typically that would be a Routine Activity stage that calls an sdk routine, either UtilityWarnToLog or UtilityAbortToLog.

Or just upgrade to get yourself all the goodness 7.5.x has to offer, which goes way beyond significant enhancements to Sequence jobs. As our good friend Mr Kim would say, 7.0 sucks.

[ray.wurlod]

"Serks", actually - Kim is in Texas.

[chulett]

Was going to spell it with a Texican accent, but wasn't sure it would be understood.