|
Walden's suggestion of sorting by wasted space is a neat one. I had accomplished this in my reorg scripts, though they're not nearly as refined as you plan for yours to be. You could keep your scope about as simple as it is now by driving your process off of DSPFD instead of DSPOBJD: DSPFD FILE(&LIB/*ALL) TYPE(*MBRLIST) OUTPUT(*OUTFILE) FILEATR(*PF)... After the DSPFD I run the output through a query, which extends the number of records out to the amount of wasted space. The query includes the following calculated for the report/outfile: Field Expression PCT MLNDTR * 100 / (MLNDTR+MLNRCD) WASTE PCT/100 * MLSIZ2 Then I sort by WASTE instead of the number of deleted records in the query's outfile, much as you do, though I do it all manually. The DSPFD command is good one stop shopping for all members, sizes, and record counts. Of course you're pretty far along with a good design and strategy. I can't imagine you'd want to gut the code now. -Jim James Damato Manager - Technical Administration Dollar General Corporation (615) 855-4375 jdamato@dollargeneral.com -----Original Message----- From: Dan Rasch [mailto:drasch@mail.win.org] Sent: Monday, May 14, 2001 11:30 AM To: 'MIDRANGE-L@midrange.com' Subject: RE: Retrieve System Status Yes, it is not perfect, but the record lengths of the files do not vary wildly, so the extra effort to compute the real size of deleted records is, well, 'out of the scope of this project.' Besides, the RTVMBRD gives me an easy NBRDLTRCD variable to work with. We are trying to clean up some age-old neglect, and hope to accomplish this by biting the bigger (not necessarily biggest) chunks first. Eventually, when our remote sites have run this for a few weeks, they will see a big improvement in their DASD. To answer the previous post on how I accomplish this, the steps are fairly simple: 1. DSPOBJD &lib/*ALL to an *OUTFILE 2. Read the *OUTFILE, and write the lib,file,current recs,deleted recs to a file keyed descending by the deleted recs 3. Read the file and run a reorg for each record (I check for the number of deleted records to exceed a threshhold 4. I also have a time stored as a stop time and check it before starting the next reorg Dan Rasch - because if the human species concentrated on the really important things in life, there would be a shortage of fishing poles! On Mon, 14 May 2001, Walden H. Leverich wrote: > Dan, > > Might I suggest also allowing the sort on deleted space not # of records. > 1,000,000 deleted records in a 10 byte record is meaningless, but 100,000 > records in a 2000 byte record isn't. > > -Walden > > -----Original Message----- > From: Dan Rasch [mailto:drasch@mail.win.org] > Sent: Friday, May 11, 2001 4:12 PM > To: MIDRANGE-L@midrange.com > Subject: Retrieve System Status > > > > I am writing an intelligent reorg program that will sort an outfile > descending by number of deleted records and then reorg files in that > order until a time value is reached. The program is already operational, > but I would like to add a before reorg message of the %ASP used and > an after message, giving the users an idea of how much disk we recovered. > > I may even go further to tell them how much storage (instead of a percent) > was regained. > > I could do a WRKSTSSTS and parse it, but a retrieve is alot cleaner. > Is there an API or such I could use here? > > Thanks, > Dan Rasch - because if the human species concentrated on the really > important things in life, there would be a shortage of fishing poles! > > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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.