start again a job sequencer only on the jobs in failure

auvray.muriel · Post by **auvray.muriel** » Sun Jul 11, 2004 11:40 am

Hello,

I read in the post

"difference between Datastage' S release 6x and 7x"

that one could start again a job sequencer only on the jobs in failure. How to make? Is it about a new functionality of V7?

Thank you for your help

Muriel

kduke · Post by **kduke** » Sun Jul 11, 2004 12:59 pm

You need Ds7.1. It is built into a sequence and works great.

auvray.muriel · Post by **auvray.muriel** » Sun Jul 11, 2004 1:40 pm

I am in version 7.1 :D , but how is that set up?

Muriel

kduke · Post by **kduke** » Sun Jul 11, 2004 4:34 pm

It is setup automatically. You have to tell it to not restart a specific job. There is a checkbox for that. In the job activity stgae it says "Do not checkpoint". Do not check this box.

In the job properties there is a checkbox for "Add checkpoints so sequence is restartable on failure". Check this box.

The next checkbox in the job properties is "Automatically handle activities that fail". Check this box.

Next you need an Exception Handler. This stage is not on the normal job stream. We link this to an Email Notofication and then to UtilityAbortToLog.

kduke · Post by **kduke** » Sun Jul 11, 2004 6:57 pm

The Exception Handler is only executed when a job fails.

auvray.muriel · Post by **auvray.muriel** » Mon Jul 12, 2004 11:57 am

Thank you very much.

Is it obligatory to have a stage "Exception Handler" in the Job Sequencer so that that functions??
If so, I did not understand at which place I must positioned.

In entry of each job must it be?
Like the drawing below ?

Code: Select all

JobActivity_01------------------------> Sequencer --------------->JobActivity_02
                                       ^
                                       |
Exception Handler ----------------------

Muriel

kduke · Post by **kduke** » Mon Jul 12, 2004 12:24 pm

I am not sure it works without it but it does not link up to the main job flow.

Job1 -> Job2 -> Done

Exception -> Email -> AbortToLog

Make sense?

auvray.muriel · Post by **auvray.muriel** » Mon Jul 12, 2004 12:26 pm

Thank you beacoup, I will carry out a test.

Muriel

auvray.muriel · Post by **auvray.muriel** » Mon Jul 12, 2004 1:02 pm

I have just made the test, and it is not obligatory to have the training course "Exception".

It's cool :D

Still thank you

Muriel

lebos · Post by **lebos** » Thu Jul 15, 2004 12:38 pm

I don't know why, but my AIX DS 7.1 system is acting differently.

I have a job sequence which has two job acitivities, JobA and JobB. These jobs are independent (they each load a different table) and are not connected in any way in the sequence. JobA has two triggers one handling failure, the other everything else ("otherwise" - goes only to a sequence with no further steps). On a failure of JobA, an email is sent and no other steps exist. JobB has only an "OK" trigger which leads to a sequence with no subsequent steps. (This is a test job afterall :D )

When I force JobB to fail (giving it a non-existent database name) and allow JobA to succeed, the sequence simply ends up "Finished", not "Finished/Restartable". The job property checkbox for "Add checkpoints so sequence is restartable on failure" is checked and neither job has the "Do not checkpoint" box checked.

I have tried other setting, with and without automatic error handling, etc, but nothing seems to work. Any thoughts?

Larry