|
What does RCLSTG accomplish, and is there a method to predict it's outcome? ( ... )
It's a good tool since on a big system it's tricky to predict how many damaged objects you may encounter. It should be a must for heavy journalized systems, since many damaged objects regard the receivers.
RCLSTG touches ownership and addressability too. A power failure or an abnormal *IMMED job end can leave traces. If an *AUTL remains damaged the real adresability of an object is affected, since a lot of information gather to define it ( *AUTL, *USRPRF, *OBJD, ... ). The RCLSTG will do a RCLAUTL that can enlighten or solve the bug. Not owned objects are sent to QDFTOWN.
You may have other lost objects. Make a RTVDSKINF then a PRTDSKINF. Page 1 gives you ' OBJ NOT IN A LIBRARY ' information. Page 3 gives you estimated space gain after RCLSTG.
You have a DTAARA somewhere in QUSRSYS ( QSYS ? ) to pick up information about your system's last RCLSTG, to estimate the time effort. IBM docs must explain somewhere the structure of this DTAARA.
Damaged objects are sent to LIB ( QRCL ). Study them, restore useful ones and delete the others. If the size of those objects is significant, RCLSTG can indeed improve the % of used storage. If nobody cleaned QRCL after several RCLSTG, it's size could be increased. See in page 3 of PRTDSKINF the actual size of your QRCL lib. Follow the rules from the books : Sys Oper, Basic Backup & Basic Security if you need recovery.
Be sure to have enough auxiliary storage for swapping operations internal to RCLSTG.
Personally I use it every three months, as you also did. On all CISC & RISC machines I met it ran no more than four hours, but the system must be restricted so it requires ... another lost week-end if you are in charge ...
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.