×
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.
I agree with the method you have outlined, as I have had experience within the last 8 years of doing that same idea in order to apply a vendor update. However, the file had way more than 20,000 to 30,000 rows in it. As I recall, it was in the millions or possibly billions of rows. The runtime saved was in terms of hours, and I am thinking it was at least 24; it was substantial. Each row in the file was touched by the vendor update process, so each LF index was "touched". Deleting the LFs, running the update over just the PF, and then recreating the LFs got the update down to about 6 hours [including the LF rebuild] or so, which was significant, since we were thinking we could not upgrade over the weekend because the rebuild took so long. That was on a V5R4 machine at the time.
Removing the LFs did greatly improve the processing time, but the file did have a ton of records in it [it was a sales tax history file].
Doug
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Questionable practice in file handling in CL, (continued)
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.
midrange.com
