Re: IFS allow save object attribute?

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

One thing to think about is that save while active of IFS is a sick joke.
So much of the stuff in there considered expendable is flagged that way as
it will never get saved with a backup while the system is live.  Examples
are log and trace files.  Some would even be a conflict in a restricted
state, like maybe BRMS log files.  And it's not just that they will get
skipped on a save, if a process tries to use it when it is temporarily
locked by a save it may abort the process.

I, too, flag the image catalogs as not to save.  They are huge, slow down
the save, and I plan on them not being there.  I suppose if I just had to
have them I could flag them as allow save but I don't tend to get so far
behind on hardware that I need to save my image catalogs to unload/reload
on to newer hardware and then upgrade the OS on the new hardware.  My save
instructions note this 'just in case'.

I've done numerous unload/reloads and never has IBM's use of ALWSAV(*NO)
been a problem.

On Wed, May 8, 2024 at 8:51 PM James Ash via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> I'm trying to clean up my IFS backups and I've had problems in the past
> with objects not being saved because the attribute to allow an object to be
> saved was *NO.
>
> I'm having a hard time grasping why I wouldn't want to save this object
> (or any object) on my system and why this attribute even exists. It just
> seems like a setup for failure.
>
> If I change all the *NO attributes to *YES, am I causing the failure of
> some process or is this all just about saving space and time on my backups?
>
> Jim Ash
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.