Msg : Sequencer 'Sequencer_28' was entered, but never exited

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
ratuldey
Participant
Posts: 33
Joined: Fri Jul 13, 2007 4:50 pm

Msg : Sequencer 'Sequencer_28' was entered, but never exited

Post by ratuldey »

DataStage version : 7.5.2 Server Edn.
OS platform : UNIX

Job Sequence Name : seqMinor1
No. of Jobs : 20
All jobs connected to the Sequencer stage ( 'Sequencer_28' ). The Mode in Sequencer set to "All". The Sequencer connected to a Message stage. This is meant to sent emails to specific mail IDs on successful run of all the jobs.

When Sequence is run, all jobs are run with Success, with a few having warning messages, but none of them gets aborted.

Problem : No mails are received although log says, "Job Sequence finished successfully". Additional message is shown as ---

"seqMinor1..JobControl (@Coordinator): Note: Sequencer 'Sequencer_28' was entered, but never exited"

I would like to know is the Sequencer ('Sequencer_28') facing any problems. Why are we receiving the message as above. Are we really into some trouble?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Welcome aboard.

The message means that not all the inputs to Sequencer_28 fired. That is, one (at least) of them did ("Sequencer_28 entered") and the overall sequence ended because everything finished - however one of the activities upstream of the Sequencer did not trigger the output that leads to the Sequencer. For example, if it had an OK trigger to the Sequencer and did not finish OK, this situation would obtain.

DataStage logs the alert so that you are aware that this situation occurred.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

This is a result of setting the Sequencer to 'All'. It is telling you that not all triggers that feed it 'fired' so it did not trigger its output link. That as a result of the jobs 'having warning messages' I'd wager, as that isn't really considered 'Success' if all you are using are 'OK (Conditional)' triggers.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply