Re: SAVSYS running over an hour

rob@xxxxxxxxx wrote:

I've got a little wimp lpar that's guested on another lpar. It's
in a restricted state. Just finished RCLSTG and I am running the
SAVSYS. Nice LTO3 tape drive. SAVSYS on this normally runs in
28 minutes (I can pull stats for over a year's worth of data on
length of run). Now it's been running over an hour. Hmm, maybe I
should have looked into why our percent used changed so much...

What exactly was the RCLSTG request? Was that RCLSTG
SELECT(*ALL) OMIT(*DBXREF)? If RCLSTG with shipped defaults, then
the reclaim could have some [should be little for SELECT(*ALL)]
asynchronous activity in one of the highest priority jobs [i.e.
QDBSRVXR] and another [i.e. QDBSRVXR2]. The amount of async
activity would be significantly more for the request to RCLSTG
SELECT(*DBXREF). That work could impact the work at the RUNPTY(10)
console job.

Unless the "percent used" of the system was due to more users
[SAVSECDTA] or configurations [SAVCFG], I would not expect that to
impact the SAVSYS request. I would suspect that the most likely
cause for longer save time would be for "large" percentage of owner
& authority entries in a\some user profiles, impacting the SAVSECDTA
portion of the save system request; perhaps someone was issuing a
bunch of GRTOBJAUT requests :-) Review the PRTPRFINT *ALL.

Regards, Chuck
--
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.