|
Dale and Others, I appreciate the additional comments. I am planning on starting tomorrow as soon as possible after a scheduled power outage. At least that way it has a day and a half to hopefully finish. Unfortunately I do not have the disk space to copy it before doing the reorg, but should have fresh backups from tonight's run. Lets hope I do not need them. Keep your fingers crossed. Thanks Scotty ____________________________ Scotty Muir Sr. Systems Programmer Triangle Suspension Systems DuBois, PA. -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On Behalf Of Dan Bale Sent: Friday, March 22, 2002 2:54 PM To: midrange-l@midrange.com Subject: Re: Freeing Deleted Disk Space Oh my. Depending on the size of the file, the system, and a few other minor (?) factors, the reorg could take anywhere from a few seconds to several days! IIRC, there's no way to safely kill a reorg once it has started. Yes, submit it to batch, but to be on the safe side, don't do it 20 minutes before a "big" long-running process needs to use it. Me, if this were the first time and I needed to get a benchmark, I'd submit it at 5pm Friday, and make sure that, if it ran all weekend, nothing else would get hung up by the file being allocated *EXCL. Make sure you set that job to log messages and check the job log Monday morning. If I had the disk space and was unsure about the time it would take for the reorg to complete, I'd first CRTDUPOBJ the physical and all its logicals to a temporary, one-time-use library, and test the reorg on that. My .02 Dan Bale working from home today ---------- Original Message ---------------------------------- From: fiona.fitzgerald@notes.royalsun.com Reply-To: midrange-l@midrange.com Date: Fri, 22 Mar 2002 16:20:47 +0000 > >Scotty, > RGZPFM PFname - but submit it to run in batch ! It might take an >hour. >Fiona > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. > > _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.