× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. September 2001

RE: Reducing Batch Job Run Time

Another thing you might consider is avoiding random I/O if there's no need
to update records in place.  You can save amazing amounts of time using
sequential I/O.  Sometimes writing all records out to a work file and
replacing the original file can be faster than updates.

> -----Original Message-----
> From: Ray Nainy [mailto:ray_456@hotmail.com]
> 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 thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.