Re: [7.3] IFS save 21 vs. sav with chgperiod (no BRMS!)

You do realize, that even in a full restricted state save, you will not be
able to save anything in /QSR since they will always be locked?

So you can choose between ATR(*ALWSAV) VALUE(*YES) and getting
Message ID . . . . . . : CPFA09E Severity . . . . . . . : 40
Message type . . . . . : Diagnostic
Message . . . . : Object in use.

or ATR(*ALWSAV) VALUE(*NO) and getting
Message ID . . . . . . : CPD37C3 Severity . . . . . . . : 20
Message type . . . . . : Information
Message . . . . : Cannot save
Cause . . . . . : The ALWSAV attribute on ... was set to *NO preventing
the object from being saved.

And whatever other messages in the joblog are generated, like summary
messages.
One is a sev 40 and one is a sev 20
Your choice.

On Thu, Feb 13, 2025 at 10:52 AM Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello Rob,

Am 13.02.2025 um 14:45 schrieb Rob Berendt <robertowenberendt@xxxxxxxxx>:

just to throw a squirrel to distract you, you might want to take a look

at

https://www.ibm.com/support/pages/how-collect-saverestore-flight-recorders

Thanks for that! While resetting the alwsav flag to yes, I stumbled over
this very directory /QSR. Now I know what it's good for.

:wq! PoC

--
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.