|
It may not be the best solution for this case, but I did this never-ending batch job on one machine to improve performance in a case where a "convoluted migration" and "postponed diskspace upgrades" resulted in a very slow open to get selected customer values. Maybe ten seconds sometimes. The interactive job sent a data queue request to the batch job, and the batch job returned the data in another queue. Bam! Seemed like lightning response. You want to make sure you consider security, users, etc., when you do this, though. - Alan ----- Original Message ----- From: "Scott Klement" <klemscot@xxxxxxxxxxxx> | The best performance will come from having jobs that do not end that are | running in batch.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.