|
I see no problems with this - seems to me, that you could end up with a smaller file - only active records, for the most part, no wasted space for deleted records.Hardly. Suppose an application program _inserts_ (or writes) 100,000 rows (records) into this table (or file), then later, another application program _deletes_ 50,000 (not necessarily contiguous) records. There will now be "wasted space" for 50,000 rows or records, regardless of the setting of REUSEDLT *YES or *NO. So, you could still need to use RGZPFM occasionally if you really want to get file sizes down to the "minimum". /*
Just curious, do you have something in mind that might cause problems?
Vern
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.