Paralell running of same job with different parameters
Moderators: chulett, rschirm, roy
Paralell running of same job with different parameters
Hi !
I wonder if I can to run one job in paralell with Sequencer stage of Job Sequence and with different Job parametr.
For example I do three Job Activiteis in Job Sequence . Each Job Activity Run the same Job with different parameters and all three jobs are related to Sequencer stage with mode ALL
I wonder if I can to run one job in paralell with Sequencer stage of Job Sequence and with different Job parametr.
For example I do three Job Activiteis in Job Sequence . Each Job Activity Run the same Job with different parameters and all three jobs are related to Sequencer stage with mode ALL
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
If it's the same job it must be capable of multiple-instance running, and you must start the three instances with unique instance IDs. An instance ID can be any string, so you can make it meaningful within your overall scheme of things.
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.
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 437
- Joined: Fri Oct 15, 2004 6:13 am
- Location: Pune, India
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
See immediately preceding post.
You create ONE job. You check the Allow Multiple Instance check box in its job properties.
Recompile.
When you run the job there is a new field, InvocationID. That's where you tag it if running from Director. If running from dsjob, use the "dot" notation mentioned earlier.
You create ONE job. You check the Allow Multiple Instance check box in its job properties.
Recompile.
When you run the job there is a new field, InvocationID. That's where you tag it if running from Director. If running from dsjob, use the "dot" notation mentioned earlier.
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.
-
- Premium Member
- Posts: 353
- Joined: Wed Apr 06, 2005 8:45 am
Hi Kirtikumar,
I have built a job seq where I have 2 Job activities with the same job, and in the job properties I have checked the "Allow Multiple Instance" , recompiled it.
Still in the job activity properties, under the job page, I am unable to find textbox called Ivnocation ID Expression.
It does ask me to assign the values at run time on a box to the right hand side.
Am I mising something here
Thanks,
I have built a job seq where I have 2 Job activities with the same job, and in the job properties I have checked the "Allow Multiple Instance" , recompiled it.
Still in the job activity properties, under the job page, I am unable to find textbox called Ivnocation ID Expression.
It does ask me to assign the values at run time on a box to the right hand side.
Am I mising something here
Thanks,
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Make sure you have checked the "Allow multiple instances" on the server job, not the sequence job.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Yes, the invocation ID must be set at run time.
The only property available at design time is "Allow multiple instances".
You do not, cannot, set the invocation ID at design time in the job.
When you fill in the job name in the Job Activity in a job sequence, use the dot notation - jobname.invocationID
The only property available at design time is "Allow multiple instances".
You do not, cannot, set the invocation ID at design time in the job.
When you fill in the job name in the Job Activity in a job sequence, use the dot notation - jobname.invocationID
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.
-
- Premium Member
- Posts: 353
- Joined: Wed Apr 06, 2005 8:45 am
-
- Premium Member
- Posts: 353
- Joined: Wed Apr 06, 2005 8:45 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The prompt for invocation ID should still appear when you're requesting a job run in Schedule view, so you fill the value in in exactly the same way as you would from a regular run request.
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.