RE: Reclaim Resource

How an object is *DAMAGED*? 
TIA
-Murugesh.

-----Original Message-----
From: JOberholtzer@xxxxxxxxxxxx [mailto:JOberholtzer@xxxxxxxxxxxx]
Sent: Tuesday, April 20, 2004 5:55 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Reclaim Resource







<snip>
Could you possibly have meant RCLSTG, "Reclaim Storage"? That's a
different animal altogether. It could take minutes, hours, or maybe even
days.
</snip>

James is correct, there is no real good way to predict, however you can
make a SWAG at it.

In the past I have done a DSPOBJD *ALL/*ALL  to an out file.  Then use SQL
to find any damaged objects.  If there are damaged objects, you can count
on a longer, rather than shorter run.  On my 170 at home (241 CPW and 32gig
Storage) a RCLSTG took about 45 minutes to complete just before an OS
upgrade.  There were a couple of damaged objects, and they were repaired
correctly.  With no damaged objects, it ran in about 10 minutes.  Keep in
mind that CPW, storage, and most importantly object count, are the main
determiners of how fast it will go.  The longest one of our clients has
seen in some time is 6 hours.   If you can plan to kick it off Saturday
night, (After Backups of course) you should have little problem finishing
by Sunday start of business.


Jim Oberholtzer
Senior Solutions Architect
Computech Resources, Inc.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.