I've run into a situation where I need a job that can be called at many different times by many different control jobs. The chance that the job could be called at the same time by two different control jobs is VERY likely.
Therefore, I looked into making the job a multiple instance job. This sounded like a good idea until I realized that every instance has to have a unique invocation id and the jobs do not clean themselves up after running. I could make this work by having the control jobs create a numeric datetime string as the invocation id, but how do you handle the cleanup?
Would like to hear tips about ultilizing multiple instance the best way.
thanks,
Greg
Multiple Instance Usage - Best Practices
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 273
- Joined: Wed Oct 18, 2006 12:20 pm
- Location: Porto
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Multi-instance jobs are intended for almost precisely the situation you're in, perhaps also for continuously-running jobs or jobs that use the RTI components (and might be invoked from lots of places).
I agree that non-selective log purge is an issue, but you can code around this or just rely upon auto-purge based on a run count.
I agree that non-selective log purge is an issue, but you can code around this or just rely upon auto-purge based on a run count.
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: 612
- Joined: Thu May 03, 2007 4:59 am
- Location: Melbourne
Re: Multiple Instance Usage - Best Practices
If you make your control job<b>s</b> pass an invocation id which is specific to it (ie. same) every time to invoke the job which is set to 'reset and run if required', you can over write on the instances and avoid instance ids piling up on timestamps.gsbrown wrote: I could make this work by having the control jobs create a numeric datetime string as the invocation id, but how do you handle the cleanup?
Note: This is under the assumption that same control job does not call the same job instance multiple times at the same time.
Joshy George
<a href="http://www.linkedin.com/in/joshygeorge1" ><img src="http://www.linkedin.com/img/webpromo/bt ... _80x15.gif" width="80" height="15" border="0"></a>
<a href="http://www.linkedin.com/in/joshygeorge1" ><img src="http://www.linkedin.com/img/webpromo/bt ... _80x15.gif" width="80" height="15" border="0"></a>