|
Well, maybe (depending on the shape for the data in the file) an alternative you could do somthign laong the following lines: - Drop the indexes and rename the source file - create a new file with the source files old name - read the renamed file sequentially using blocking etc - Write each record to whichever of the files the timestamp of each record dictates - rebuild the indexes on the new source file This would avoid a re-org, allow the read portion to be optimized and could even include the approach of reading the source file using record ranges. Without knowing the data make-up it's hard to suggest what might be the most optimal approach. I figure the above approach might be the best if the number of records to be deleted and retained is reasonably similar. Hope this helps Evan Harris >Also ... the big time consumer is still there .. REORGING THE FILES .. to >recover the DASD..! .. This process is dependent on the number of Logical >files as well as the size of the original physical file! .. This is still my >favored archiving solution. +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.