Weired behaviour of sequence job
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 132
- Joined: Wed Mar 01, 2006 11:12 pm
- Location: Pune
Weired behaviour of sequence job
I have a sequence job wherein I am using the sequencer stage to run around 25 jobs concurrently. The issue is that the final status of my main job is showed finished but some of my jobs in the sequenc are untouched.
For example
Suppose I have a sequence job "Jobmain" where, after the completion of activity "job1" the sequencer stage passes the control to 25 job activity stages say "job2", "job3",..."job26". When I run the job "Jobmain", in director the status of the job "Jobmain" shows as finished. but some jobs say "job3" , "job5", etc still shows status as compiled. I need to run the "jobmain" multiple times untill I get the status of all the jobs as Finished.
This has been happening for everytime i run the job "jobmain".
I am unable to understand the behaviour. Has anyone faced a similar issue. Can anyone suggest me some solution to this problem.
For example
Suppose I have a sequence job "Jobmain" where, after the completion of activity "job1" the sequencer stage passes the control to 25 job activity stages say "job2", "job3",..."job26". When I run the job "Jobmain", in director the status of the job "Jobmain" shows as finished. but some jobs say "job3" , "job5", etc still shows status as compiled. I need to run the "jobmain" multiple times untill I get the status of all the jobs as Finished.
This has been happening for everytime i run the job "jobmain".
I am unable to understand the behaviour. Has anyone faced a similar issue. Can anyone suggest me some solution to this problem.
SMB
-
- Premium Member
- Posts: 273
- Joined: Wed Oct 18, 2006 12:20 pm
- Location: Porto
Is it possible to post the job design ? I mean the figure of the job design..
In case you want to trigger all job2 to Job26 in parallel, then you may create another Job Sequence and place all the 26 jobs in that..but none connected to each other (so that they are triggered in parallel).
I am suggesting something like this for the design of JobMain:
JobSeq_New will contain all the jobs from Job2 to Job 26, remem without any connection.
HTH.
In case you want to trigger all job2 to Job26 in parallel, then you may create another Job Sequence and place all the 26 jobs in that..but none connected to each other (so that they are triggered in parallel).
I am suggesting something like this for the design of JobMain:
Code: Select all
Job1---->JobSeq_new
HTH.
Share to Learn, and Learn to Share.
-
- Participant
- Posts: 132
- Joined: Wed Mar 01, 2006 11:12 pm
- Location: Pune
I cannot run the jobs without them being connected as for the Job1 if the User status is 'Completed' then it calls these jobs Job2 to Job 26 and if the user status of all Job2 to Job 26 is 'Completed' then I am updating the control table. So it they are not connected then It wont be possible to check the combined user status which I am currently doing.asitagrawal wrote:Is it possible to post the job design ? I mean the figure of the job design..
In case you want to trigger all job2 to Job26 in parallel, then you may create another Job Sequence and place all the 26 jobs in that..but none connected to each other (so that they are triggered in parallel).
I am suggesting something like this for the design of JobMain:JobSeq_New will contain all the jobs from Job2 to Job 26, remem without any connection.Code: Select all
Job1---->JobSeq_new
HTH.
SMB
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 273
- Joined: Wed Oct 18, 2006 12:20 pm
- Location: Porto
Code: Select all
Job1--<Check Trigger Condition>-->JobSeq_new---<Check the trigger condition>---->JobUpdateControlTable
So, depending on the required conditions, you can then execute the job to update the control table.
HTH
Share to Learn, and Learn to Share.
-
- Participant
- Posts: 132
- Joined: Wed Mar 01, 2006 11:12 pm
- Location: Pune
Thanks for the advise...asitagrawal wrote:You can check the status of JobSeq_new... If all the 25 jobs, Job2 to Job 26 have finished , then only the status of JobSeq_new would be finished and the control will be transfered to the next item.Code: Select all
Job1--<Check Trigger Condition>-->JobSeq_new---<Check the trigger condition>---->JobUpdateControlTable
So, depending on the required conditions, you can then execute the job to update the control table.
HTH
It worked... :D
SMB
-
- Premium Member
- Posts: 273
- Joined: Wed Oct 18, 2006 12:20 pm
- Location: Porto