Re: The RCLSTG mystery...

Dan Rasch wrote:

What does RCLSTG accomplish, and is there a method to predict it's outcome? ( ... )

RCLSTG targets the logical level, not the physical one as Microsoft SCANDISK does on PC's. It isolates damaged and lost objects and tries to recover them.

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 ...

For a storage gain if you use big outputs, also consider RCLSPLSTG. On old systems with little maintenance it will help.
 

Andre
_________________________
acentea@forzani.com
centea@dsuper.net +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---