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

Hello Rob,

thanks for chiming in!


Am 13.02.2025 um 13:43 schrieb Rob Berendt <robertowenberendt@xxxxxxxxx>:

Trying to see how many questions you are asking.

Touché. :-)

1 - Are certain files not saved? Yes. To turn it on for a file it would be CHGATR '/mydir/myfile' ALWSAV(*NO).

Ah, now I remember! Thanks!

IBM does this for many files that are simple logs.

Makes sense. I don't care about logs in the IFS. But taking samples on the log being generated by sav shows much more than logs. Example:

/QIBM/ProdData/LicenseDoc/G544-5767-08/G544-5767-08_en

Keep in mind that save while active of IFS stuff is a sick joke. So IBM feels the message id for 'this item was not saved because it was flagged not to save' can be handled differently than 'this file was not saved because it was locked'.

I see. Well, since I'm not really

2 - *lastsave: When using that, did you set the UPDHST(*YES) on the save everything save?

For me, this is GO SAVE option 21. I can't change individual settings here.

The default is *NO.

Is this maybe only true for IFS? For savchgobj and savdlo, it apparently updates the history. Also, it updates the history on V4R5, because if there are no changes, objects don't end up in the according sav.

GO SAVE, 21 defaults to UPDHST(*YES).

Okay, we're on the same track again.

3 - Recommendations regarding the save to alternative media. I'm going to
pass on this.

I'm not asking about alternative media, but how to correctly deal with the issue I'm experiencing regarding differential saves from IFS objects being more wholesome than necessary.

:wq! PoC