|
The thing I would do would be to submit each of the 10 different programs at one time. If you have a single threaded job queue, that won't help you, so you may want to create or modify a job queue to allow more than one job to run at a time. SBMJOB CMD(CALL PGM(MYLIB/MYPGM1)) JOBQ(MULTIJOB) SBMJOB CMD(CALL PGM(MYLIB/MYPGM2)) JOBQ(MULTIJOB) SBMJOB CMD(CALL PGM(MYLIB/MYPGM3)) JOBQ(MULTIJOB) . . . That would allow them to run all at once, and you may get an exceptional increase in the total process time (1/10th the time or 24 minutes) or next to no saving at all, depending on what is taking the jobs so long to run (is it CPU time, DASD wait time, etc...) Regards, Jim Langston Programmer/Analyst Cels Enterprises, Inc. -----Original Message----- From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On Behalf Of Ray Nainy Sent: Thursday, September 06, 2001 12:37 PM To: RPG400-L@midrange.com Subject: Reducing Batch Job Run Time Hi all, What are the best options available to reduce the batch job run time? We have a daily batch job which runs about 4 hours, and which calls 10 different programs. All these programs are independent of each other and can be called in any sequence. Looking for best options to reduce the batch job run time. thanks in advance. Ray
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.