DSXchange

Hi,

In my first attempt to build job sequences I had to meet the requirement that on failure of a jobrun any other job that is running in parallel should finish first before the jobsequence itself gets aborted. I used a terminator stage with the option 'stop request, wait for other jobs to finish' and had all jobs have a fail link pointing to the terminator stage.

I did not choose to use the option 'automatically handle activities that fail' because the ascential documentation is not clear if any other running jobs are aborted as well or will finish first. Since this option would not require any failure links to be defined the result would be a clearer design.

Is anyone having experience with the automatic exception handling regarding jobs running in parallel?

Martin Werkman

DS 7.5
EE 7.5
Oracle

Hi and welcome aboard ,
Automatic handle activities that fail:
1. will trigger the exception handler stage.
2. will do the above in case no trigger except finished ok was set for a job activity otherwise it will assume you handled that activity's failiour.
3. Routines are concidered successfull if their return vallue is set to 0 as does all Ascential exisitng routines, if your custom routines return values like strings or calculated results other then 0 they will be treated as failed (concidering previously mentioned behaviiour).
4. once an exception is triggered you can get it's triggering activity's name,error code and dscription to pass along any following activity.

P.S:
Please test all of the above, before implementing; no waranty givven.

IHTH,

Even server jobs are allowed to finish with the exception handler logic in place. I assume PX jobs do the same. The sequence is aborted long before these other jobs are finished. That is important when restarting. You need to check to see if all jobs are finished in that sequence before restarting.