Hi,
I designed a job sequence (call it Mainseq1) to run two other job sequences (call them Subseq1, Subseq2) in parallel.
MainSeq1:
------------
UserVarAct1--->Subseq1JobAct
UserVarAct2--->Subseq2JobAct
Although Mainseq1 is starting Subseq1, Subseq2 in parallel, actually Subseq2 is waiting for Subseq1 to finish.
Both Subseq1, Subseq2 are in running status at the same time. While Subseq1 is executing its activities in the order, all Subseq2 does is initialize its environment variables and wait (Observed from job log). Subseq2 is resuming with its activities only after Subseq1 is finished.
Looking for inputs on the above issue. Your help is greatly appreciated.
Regards
Sri
Running Jobs in parallel from Job Sequence - Job waiting
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Not enough information. We have no idea what these jobs are doing, and therefore no idea why the second job may be waiting. For example it may be locks or semaphores within DataStage itself (that you have elected to use to synchronize events), it may be locks in a database, it may be other things. Tell us.
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: Running Jobs in parallel from Job Sequence - Job waiting
I figured what the issue is. I am calling a sequence generator concurrently in both the subjobs using KeyMgtGetNextValue.sri1dhar wrote:Hi,
I designed a job sequence (call it Mainseq1) to run two other job sequences (call them Subseq1, Subseq2) in parallel.
MainSeq1:
------------
UserVarAct1--->Subseq1JobAct
UserVarAct2--->Subseq2JobAct
Although Mainseq1 is starting Subseq1, Subseq2 in parallel, actually Subseq2 is waiting for Subseq1 to finish.
Both Subseq1, Subseq2 are in running status at the same time. While Subseq1 is executing its activities in the order, all Subseq2 does is initialize its environment variables and wait (Observed from job log). Subseq2 is resuming with its activities only after Subseq1 is finished.
Looking for inputs on the above issue. Your help is greatly appreciated.
Regards
Sri
This issue got resolved after replacing KeyMgtGetNextValue with KeyMgtGetNextValueConcurrent.
Thanks for responding.