RE: Reclaim storage

Bah!  I haven't done a RCLSTG in years!  ;) 


--
Justin C. Haase - Solution Engineer
IBM Certified Systems Expert - System i
Kingland Systems Corporation

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] 
On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, January 03, 2007 8:39 AM
To: Midrange Systems Technical Discussion
Subject: Re: Reclaim storage

How long will a RCLSTG take?  It's a big WAG.  I keep very detailed records.  I 
can go back a couple of years, but I'll just post the last few dates.  The only 
thing you can go by is how long that particular lpar took in the past.  I have 
had some release upgrades slow it down dramatically. 
And IBM had me do extensive traces, etc.  I sure wish all the early ship people 
did befores and afters on this sort of stuff instead of thumping their chest 
that they haven't run a RCLSTG in years.
My times may be meaningless to you.  After all, do you have more free space 
than you have in all "user libraries" as according to PRTDSKINF *SYS?  Is a 
vast percentage of your space eaten up by IFS?

System  Date of   RCLSTG
Name    Downtime    HH:MM
GDI     2006-11-17   1:27   270-23F1 67% of 140GB
GDI     2006-09-21   1:26
GDI     2006-07-28   1:25
GDIHQ   2006-11-18   6:16   570-7748 lpar 86% of 4.9TB
GDIHQ   2006-07-28   6:53
GDIHQ   2006-04-07   3:33
GDIHQ   2006-02-10   3:20
GDISYS  2006-10-20   8:40   570-7748 lpar 87% of 705GB
                            after unload/reload from 520
GDISYS  2006-09-22   5:57   520-7736 lpar
GDISYS  2006-07-28   8:35
GDISYS  2006-06-02   9:54
GDWEB   2006-11-17     17   570-7748 lpar 46% of 211GB
GDWEB   2006-09-22     17
GDWEB   2006-07-28     21
GDWEB   2006-06-02      9
MAILTWO 2006-11-18     23   270-2454 94% of 703GB
MAILTWO 2006-09-25     12
MAILTWO 2006-08-03     13
MAILTWO 2006-06-06     18
WAS520  2006-09-22     21   520-7736 lpar
WAS520  2006-07-28     24
WAS520  2006-06-02     27

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Dave Snyder" <Dsnyder@xxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/03/2007 08:27 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
Reclaim storage






The renewed discussion of performing a reclaim storage reminds me that we 
have never run one on our 520 that we have been on since Oct 2005. I have 
an upcoming weekend where we will need to bring the system down to add 
some memory and also install some third-party software that requires us to 
be in a restricted state. Since we are down for those occurrences it would 
be wise for me to take advantage of the time and also run the reclaim 
storage, since down time is at a premium these days.

 

When I bring this up to management as a proposal I know I will get two 
questions:

 

1.               How long will it take?
2.               What the heck is a reclaim storage?

 

I know what it took when we were on an 820 (2 ½ hours in Feb 2004), but 
now being on a 520 (2400cpw) with more dasd (808gig / 65% utilization) and 
memory (4gig), and new release (v5r3), I am not sure of an estimate. Has 
anyone done one with conditions close to these that might be able to share 
some time estimates? I am not having any problems or receiving any 
messages that I am aware of, but if I do not take advantage of this window 
to do one now it might come back to bite me. 

 

For the second question, how do you explain it to non-technical management 
people? What Windows function can I relate it to that they might 
understand? It is not a disk defrag, maybe a scan or cleanup?

 

Thanks.

Dave 

 


***********************************************
PRIVILEGED AND CONFIDENTIAL:
This communication, including attachments, is for the exclusive use of the 
addressee and may contain proprietary, confidential and/or privileged 
information. If you are not the intended recipient, any use, copying, 
disclosure, dissemination or distribution is strictly prohibited.  If you 
are not the intended recipient, please notify the sender immediately by 
return e-mail, delete this communication and destroy all copies.
***********************************************