Hi,
We are building the Cognos cubes(unix script will build the cube) thru Datastage execute command activity. We designed the sequence job to trigger the unix scripts(which will build cube in cognos server) parallelly.
But when we run the sequence job, it is triggering the scripts sequentially.
Seq Job design is like:
Job Activity -->sequencer-->Execute comm activity1
-->Execute comm activity2
-->Execute comm activity3
Can anybody help on this please.
Thanks in advance.
Cognos Cube build issue
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Sequences NEVER run in parallel; indeed a sequence is a special case of a server job.
Why is there a Sequencer in your sequence? Does removing it make any difference?
Execute Command is synchronous (the sequence waits till the command finishes). The way around this is to start background processes using nohup in the Execute Command activities. For example:
Of course, using this approach, the sequence might well end before any of the commands ends. If this is a concern, add a downstream loop to check jobs and not exit the loop until all three are no longer present.
Why is there a Sequencer in your sequence? Does removing it make any difference?
Execute Command is synchronous (the sequence waits till the command finishes). The way around this is to start background processes using nohup in the Execute Command activities. For example:
Code: Select all
nohup buildCube.sh > buildCube.log 2>&1 &
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.