Alternate way without using sequencer

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
sirishds
Participant
Posts: 18
Joined: Sat Jun 12, 2010 11:28 pm

Alternate way without using sequencer

Post by sirishds »

Hi,

I have a couple of jobs need to be executed sequentially but i am not supposed to use sequencer is there any alternative way to perform the control flow of jobs.

Thanks in Advance
Sirish.
ETLJOB
Participant
Posts: 87
Joined: Thu May 01, 2008 1:15 pm
Location: INDIA

Post by ETLJOB »

Is there any specific reason for not using sequencers?

1. Two "dsjob" commands from the script.
2. Job schedulers.
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Re: Alternate way without using sequencer

Post by Sainath.Srinivasan »

sirishds wrote:I have a couple of jobs need to be executed sequentially but i am not supposed to use sequencer is there any alternative way to perform the control flow of jobs..
Is this another interview question ?

Do not know whether it is just me, but your questions appear to point towards specific properties by constraining all general and default options, which is typical of interviews.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

It's OK, no question was asked.
:wink:
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
prasad.bodduluri
Participant
Posts: 30
Joined: Tue Jan 30, 2007 5:21 am
Location: bangalore

Post by prasad.bodduluri »

you can use batch mode to run jobs without sequence
prasad
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

A batch IS a sequence, except for having no GUI and a specific naming convention. Similarly a job control routine IS a sequence, except for having no GUI.

Of course the really smart answer is to use a sequence.

A sequence is not a sequencer. A sequencer makes an "any/all" decision about which of its inputs has fired.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply