We still regularly do a RCLSTG just before full system saves. IF, we have
the time. The last scheduled downtime we did not because we were doing a
physical machine move to another location and could not afford the time.
IBM actually discourages it unless needed. It really doesn't help with
the saves (which is why I started doing it). We were finding damaged
objects in our full system saves causing hangs. Well, RCLSTG didn't find
them anyway. The save is what flags suspicious objects as damaged.
IBM doesn't even recommend it after power outages, several system abends,
etc
IBM will tell you events that do not justify RCLSTG, but is loath to tell
you what DOES justify running RCLSTG. Well, other than messages like
CPF2FE3, which even then don't recommend a full RCLSTG.
http://www-912.ibm.com/s_dir/slkbase.NSF/0/9373303619fb4b89862565c2007d4bcf?OpenDocument
On supported versions of the OS you should be able to run DSPDTAARA
QRCLSTG and see how long your last RCLSTG took (provided you've done one
since you've been on a supported version of the OS)
Value
Offset *...+....1....+....2....+..
0 '1110408 190139
50 '1110409 011742
100 'V7R1M0 GDISYS 103BDDD
150 'R0005704585051022
200 'F0001508409004023
250 'D0000516304000148
300 'O0005188281000055
I started ours (on this lpar) at 19:01:39 on April 8 and it ended at
01:17:42 on April 9.
Another lpar shows April 8 at 21:21:01 through April 9 at 04:07:53.
Have your objects converted before trying it, or, be very current in your
ptf's first.
https://www-304.ibm.com/support/docview.wss?uid=nas2bd72f0f082efc1f58625771a003c75bf
IOW do not run RCLSTG right after upgrading your OS before putting on
PTFs. And, that's a very recent cume.
It IS mentioned in the infocenter in the steps for "Recovering your
system". That's as close as a hint to a recommended time to run it that I
can find.
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/rzarm/rzarmkickoff.htm
Rob Berendt
midrange.com
