Sequence get stopped automtically

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
shrinivas
Participant
Posts: 53
Joined: Mon Sep 18, 2006 3:42 am
Location: hyd

Sequence get stopped automtically

Post by shrinivas »

My sequnce is getting stopped after few jobs run with out any warnings . I am getting a info in my Log stating " Stop request detected for the Sequence 'SEQUENCE NAME';

After this all other jobs running in sequence are getting stopped. Really dont know what is leading this. All the jobs are simple in nature.
vinothkumar
Participant
Posts: 342
Joined: Tue Nov 04, 2008 10:38 am
Location: Chennai, India

Post by vinothkumar »

If you are using STOP Stage in your sequence then please check the trigger conditions of all input links to this stage
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Ask - with vigour - who is issuing Stop requests (whether from Director or from dsjob command).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
shrinivas
Participant
Posts: 53
Joined: Mon Sep 18, 2006 3:42 am
Location: hyd

Post by shrinivas »

Hi guys ya I am using terminator stage (or Stop stage ) in the seq. and the condition for Tremination is when the dependent job fails. But no job is as such failed in my sequence . Its just sending a stop request to all the jobs in the sequence.
Pagadrai
Participant
Posts: 111
Joined: Fri Dec 31, 2004 1:16 am
Location: Chennai

Re: Sequence get stopped automtically

Post by Pagadrai »

Hi Shrinivas,
You need to check all the links that are leading to the Terminator stage
and one of them might have been 'Unconditional'.
Pagadrai
Participant
Posts: 111
Joined: Fri Dec 31, 2004 1:16 am
Location: Chennai

Re: Sequence get stopped automtically

Post by Pagadrai »

Hi, :idea:
One more thing you might want to check is if there are any routine activity stages that return value <> 0.
In sequences, you have the option in job properties whether to consider the non zero return values as error.
am guessing if there is a similar issue in your job.
Post Reply