RE: RCLSTG (Was: Preventative Maintenance For AS400)

[rob@xxxxxxxxx]

<snip>
Historically, it has seemed like if you do them regularly they don't
take as long.
<snip>
I don't find that to make a difference.

Here's a catch22.  We run the RCLSTG before the saves to avoid a save 
crashing because of damaged objects.  (Management central is really bad at 
creating damaged collections.)  However an object will not be marked as 
damaged prior to the first attempt to save it.

The scenario.  System is brought down to restricted state.  Unbeknownst to 
us we have yet another damaged *MGTCOL.  Doing a DSPOBJD would not have 
the damaged flag set yet.  Full RCLSTG is run.  Full system save is run. 
Crashes when we hit the damaged *MGTCOL.  At this time the DSPOBJD should 
now have the damaged flag set.

This is one of the reasons why Al Barsa recommends doing a full save 
immediately upon a full system restore.  Right Al?  It's bitter medicine 
to swallow because it significantly increases your downtime in one of your 
most stressful situations.

Now we do a SAVOBJ of all objects in QMGTC2 to a save file and delete any 
damaged ones prior to the RCLSTG.  What a pain in the bum.

Rob Berendt