running multiple jobs
Moderators: chulett, rschirm, roy
running multiple jobs
This is a problem with their scheduling system that submits jobs. They have escalated to vendor.
Last edited by tminelgin on Tue Nov 09, 2010 6:42 am, edited 1 time in total.
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard.
Their reason may be purely political or it may be a bad experience they once had where two huge jobs swamped the server or locked rows, pages or tables in the database. You need to discover the reason.
DataStage has no limits on the number of jobs running simultaneously except that any single job can not be started if it is already running. To get around that, jobs can be made "multi-instance capable" so that clones of the job with unique "invocation IDs" can be run at the same time.
Beware, of course, that every job running will demand resources. Things will be good only so long as the system can deliver those resources.
Their reason may be purely political or it may be a bad experience they once had where two huge jobs swamped the server or locked rows, pages or tables in the database. You need to discover the reason.
DataStage has no limits on the number of jobs running simultaneously except that any single job can not be started if it is already running. To get around that, jobs can be made "multi-instance capable" so that clones of the job with unique "invocation IDs" can be run at the same time.
Beware, of course, that every job running will demand resources. Things will be good only so long as the system can deliver those resources.
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.