|
We suggested 6AM to the users as the stop time, giving the last reorg two hours to run before 'the office arrives'. Funny that you quoted two hours..... 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: > Sounds good then. My only caveat would be to stop the reorg as you get > "close" to the end time. "Close" is open to interpretation, but I'd hate to > see you start a 2 hour reorg 1 minute before the end time. No way to stop > the reorg once it's started (well, I guess you could just kill the job, but > no _clean_ way). > > -Walden > > -----Original Message----- > From: Dan Rasch [mailto:drasch@mail.win.org] > Sent: Monday, May 14, 2001 12:30 PM > 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 > +--- > +--- | 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.