We're talking a whole bunch of concepts and thoughts being jumbled
together.
1 - Flagging stuff in BRMS. I was not talking about this, and "link omit
lists" in BRMS. No way, no how. I was talking solely about using
WRKLNKBRM to see when a particular directory/file was last backed up.
2 - Your BRMS backups will have messages like
Message ID . . . . . . . . : CPD37C3
Cannot save /QIBM/UserData/OS400/TCPIP/RAS/IKEV2SOCKET
The ALWSAV attribute on /QIBM/UserData/OS400/TCPIP/RAS/IKEV2SOCKET was set
to *NO
DSPLOGBRM TYPE(*BKU) PERIOD((*AVAIL 032218))
BTW, that's a sev(0) message.
If you were doing a regular SAV command there's an option to have all
these messages go to a file to make it easier to process. I don't have
the inclination to figure out how to do this in BRMS.
These should appear in your joblog also. Many people are opposed to
change so they still have all their joblogs go to a spool file. I changed
all ours to go to *PND and this allows me to query them using tools like
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/QSYS2.JOBLOG_INFO()%20UDTF
Here's an outside of the box thought...
If the directory is flagged as ALWSAV(*NO) and they feel the data is
expendable and shouldn't be saved, then shouldn't you go in and delete all
those files that are over x days old? For example, if the directory name
is .../logs... and it's flagged as ALWSAV(*NO) and there's 45,000 files in
there might that give you back some space? At least since upgrading from
7.1 you don't have to worry about these slowing down your saves or taking
up tape space.
Rob Berendt
midrange.com
