|
From what I've read in the official IBM documentation, a RCLSTG isn't
required until the system complains about needing one. Usually when it does complain, it's only for *DBXREF and that's a relatively short one to process. However, if you're going to be running an extremely important full save soon and want to be generally comfortable it won't bomb-out on damaged objects, a RCLSTG is a good way to touch every one and make sure your save will go smoothly. For example, a double-save prior to moving a system. This is the process I have followed in my 7+ years of iSeries experience and it has yet to fail me. It doesn't HURT anything to run it more frequently, and if you have the time to spare, go for it. But it's by no means required. -- Justin C. Haase - iSeries System 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 Dave Snyder Sent: Tuesday, August 15, 2006 8:02 AM To: Midrange Systems Technical Discussion Subject: Reclaim storage question Since the reclaim storage question has come up again, I am wondering if I need to do another soon. The last one I ran was on a previous box (820) and that was on Feb 1, 2004. I have not done one on this new box (520). That was on v5r1 and we are now on v5r3. We have had no abnormal shutdowns since on this 520. We went to this 520 last October so I am not overly concerned about running one, but thought I would ask. Any guidelines or hints as to how often to run one if things are going smooth, as they normally do? Is there are value to watch for a certain threshold to trigger one? 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. *********************************************** -- 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. CONFIDENTIALITY NOTICE: This e-mail communication, including attachments, is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential, and may be legally privileged. If you are not the intended recipient or believe you received this communication in error, please reply to the sender indicating that fact and delete the copy you received. In addition, retention, dissemination, distribution, copying, or otherwise use of the information contained in this communication is strictly prohibited. Thank you.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.