How to run the EXCUTE COMMAND stage parallal
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 1
- Joined: Mon May 28, 2012 1:28 am
How to run the EXCUTE COMMAND stage parallal
In a sequencer, I have to use EXCUTE COMMAND stage to run in parallal. even though we design EXCUTE COMMAND stage run in parallal in sequencer but it is excuting sequencial only. please help out..
SAT J
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard.
1. This is not a WTX (formerly DataStage TX) question.
2. Sequences do not execute in parallel. Just that. There is one sequence of control, not many.
3. What exactly do you wish to accomplish?
1. This is not a WTX (formerly DataStage TX) question.
2. Sequences do not execute in parallel. Just that. There is one sequence of control, not many.
3. What exactly do you wish to accomplish?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Re: How to run the EXCUTE COMMAND stage parallal
Execute Command stage never runs in parallel unless you drop many of them on the main sequencer to run at the same time.jpsathish26 wrote:In a sequencer, I have to use EXECUTE COMMAND stage to run in parallel. even though we design EXECUTE COMMAND stage run in parallel in sequencer but it is executing sequential only. please help out..
What you might want to look at is if you run with a configuration file that has multiple nodes (degrees of parallelism) and you wish a script to execute per degree of parallelism... Then you should look at the External Source Stage within a Job.
But... given that you are not familiar with the Execute Command Stage, it's best that you truly understand what you actually want to do before jumping into the External Source Stage process.
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
And how you are proposing to use job activity for calling script?Rakesh311 wrote:You can create Separate JOB ACTIVITY for these scripts and call it from your main seq it will work paralley..
Paul already mentioned dropping many of execute command stage in sequence job or using external source stage which I think are the correct ways to do that. Even using routines or user variable activity or shell script wrapper to call them without waiting to get the result can be used but that doesn't change the logic.
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.
Genius may have its limitations, but stupidity is not thus handicapped.
Even if you gave multiple execute command stage in a sequencer it may not work parallel especially if you are calling same script with different parameter.
For that if we create this execute command as separate seq job and if we call it as Job activity it will work in parallel.
Of course we can use external source stage for this requirement,
I just suggested one more way to do it.
Regards,
For that if we create this execute command as separate seq job and if we call it as Job activity it will work in parallel.
Of course we can use external source stage for this requirement,
I just suggested one more way to do it.
Regards,
rAKESH