Re: More tape required for backup

Maybe try the DSPLOGBRM command, how GO BRMS, then take reports option,
there are many reports to pick from, maybe one of those might help you out.

On Wed, Jan 25, 2012 at 12:21 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 25-Jan-2012 08:50 , John McKee wrote:

Our sa is away. The last two weeks, the full backup (GO SAVE 21) has
required three tapes, where it normally requires two. <<SNIP>>
do not believe usage has changed much. I am wondering if we just
stepped over the threshold that two tapes can hold. <<SNIP>>

Might be that some "manual cleanup" [periodic or while in restricted
state after the save] was being done by SA, but the now unchecked growth
has pushed the limit. That is to suggest, that sometimes those actions
do not make their way into the documented procedural steps that somebody
else might have to perform as a backup\replacement.

For example: History logs and audit journal receivers sometimes
either are not saved :-( and\or saved separately and then deleted.
Perhaps deleting all previously saved\eligible receivers, post-save.
The QRPLOBJ which maybe was getting cleared; AFaIK that library is part
of the save-21. There may also be "log files" in some directories that
were being purged, with or without prior save. And if spool data is
part of the saves, perhaps some SPLF cleanup using or outside of the GO
CLEANUP.

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.