Job control in a sequencer

[SonShe]

I have a sequencer with a few jobs in it. What I want is Job1 should trigger Job2 when Job1 is either successful or has warnings. Job1 should not trigger Job2 only when Job1 fails.

Job1 --------------> Job2 ------------------->
|
triggers Job2 when Job1 is successful or has warnings

I will appreciate any ideas or help to accomplish this.

Thanks.

[chulett]

You need to use a Custom trigger to handle this. For Ran Ok and Warnings, use something like this in the trigger to Job2:

Code: Select all

Job1.$JobStatus = 1 Or Job1.$JobStatus = 2

Note that 'Job1' in the above trigger code is actually the Job Activity stage name that runs Job1.

I'd suggest using an 'Otherwise' trigger to handle the 'not ok' part of this sequence, rather than specifically checking for Aborted.

[Sainath.Srinivasan]

Got confused with your requirement and diagram.

If you want to apply a constraint of "do not perform job2 if job1 fails", then all you need to do is to grab a link to a dummy action and insert the condition of fails to it and use 'otherwise' constraint for the job2 link.

If you want to call job2 on success or warn or job1, then you can have 2 links - one for success and one for warn - and both having job2 at its head, which then leads to a sequence stage with 'any' option.

You can carry forward from the sequence step.

[SonShe]

You need to use a Custom trigger to handle this. For Ran Ok and Warnings, use something like this in the trigger to Job2:

Code: Select all

Job1.$JobStatus = 1 Or Job1.$JobStatus = 2

Note that 'Job1' in the above trigger code is actually the Job Activity stage name that runs Job1.

I'd suggest using an 'Otherwise' trigger to handle the 'not ok' part of this sequence, rather than specifically checking for Aborted.

Craig, thank you for the help. I have another question though not directly related to my first posting. In the same sequencer where I have 3 jobs, if the first one or the second one aborts, the sequencer still continues execution of the subsequent jobs. My understanding is that the sequencer should be able to trap this job level error and act accordingly. Can you please educate me what actually happens here.

Thanks.

[chulett]

What version of DataStage 7.x do you have? The ability of the sequence to trap job level errors (via the Exception stage) was only added in 7.5, from what I recall.

Before that, you need to handle it all yourself via triggers.

[ray.wurlod]

In versions earlier than 7.5, your Exception Handler can trigger a Routine Activity that calls UtilityAbortToLog, which will abort the entire job sequence.
It's not a technique that I like (I prefer to create jobs that don't abort), but it works.

[chulett]

But in earlier versions, the Exception Handler will only 'fire' if something is wrong with the Sequence itself... a parameter it is trying to set does not exist, for example. A job failure won't trigger it.

[Sainath.Srinivasan]

In previous versions of DataStage, the exception handler will be triggered if the Sequencer cannot perform what it has been asked to do. For e.g. if you ask it to run a job that has failed in its last run.

[chulett]

... and you haven't specified 'Reset if required then run'.

Same thing I was basically trying to say. If the sequencer starts the job and the job fails, the exception handler is not triggered.