|
Martin wrote: >Program A reads a file and for each record >submits about 20 jobs to batch to update >totals further up the hierarchy of records >in the file. -snip- >At the moment no more than 3 or 4 jobs are >active at a time because Program A is not >submitting them fast enough. -snip- >Is there a way to speed up submission of >the batch jobs from program A? An interesting question. Ordinarily I would not recommend trying to submit many jobs at all - I would write a server program to listen to a data queue and have program A send entries to the data queue. As the workload increases, you can run multiple servers all listening to the same data queue. There have been posts in the past about this topic; http://archive.midrange.com/midrange-l/200006/msg00232.html is a good one. The point being that starting a brand new job is expensive; sending a parameter to an already running job is much cheaper. If you aren't able to change the architecture, investigate prestart jobs. Anything you can do to minimise the cost of the new jobs is a step in the right direction. --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.