Thanks for that SQL, I'll put it in the bag of tricks.
As to the BRMS you are right, it still takes time to backup those files and if we don't want them. It's not worth the effort. I'll have the auditor in question give you a call next year 😉.......
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Monday, May 11, 2020 9:26 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: New RFE: Have IBM flag another directory with ALWSAV(*NO)
Actually the ALWSAV(*NO) can be retrieved with a SQL command.
select path_name, object_type, object_owner, allow_save
from table(qsys2.IFS_OBJECT_STATISTICS(
start_path_name => '/QIBM/UserData/OS400/ServiceAgent',
subtree_directories => 'YES'))
where allow_save = 'NO'
limit 10;
The problem with BRMS omits is that we always use OMITS(*NO) on our dedicated full system saves. I still don't want those directories.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
<
http://www.dekko.com>
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L < <mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx> midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of <mailto:midrangel@xxxxxxxxxxxxxxxxx> midrangel@xxxxxxxxxxxxxxxxx
Sent: Monday, May 11, 2020 10:16 AM
To: 'Midrange Systems Technical Discussion' < <mailto:midrange-l@xxxxxxxxxxxxxxxxxx> midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: New RFE: Have IBM flag another directory with ALWSAV(*NO)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
We have run into auditors that faint with the vapors every time we set
*ALWSAV *NO. They claim the system is unrecoverable. (even the files for
IBM i hosted partitions) When we point out, as you do, that those files are
not needed for a recovery, they seem to be OK with the BRMS omits, since
that "documents that you are not backing them up". I'm not aware of an IBM
supplied report that shows the *ALWSAV attribute when it's no, and they
would not accept a custom report.
I love auditors........
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L < <mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx> midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Monday, May 11, 2020 9:06 AM
To: Midrange Systems Technical Discussion < <mailto:midrange-l@xxxxxxxxxxxxxxxxxx> midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: New RFE: Have IBM flag another directory with ALWSAV(*NO)
Had a backup give us some warning messages that some stream files were
locked. These were highly expendable and recreated at will. So I submitted
a RFE that IBM flag that directory with ALWSAV(*NO)
<
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=142309>
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=142309
BRMS backup is getting:
CPFA09E Object in use. Object is
/QIBM/UserData/OS400/ServiceAgent/trace/esa.log.0.lck.
CPFA09E Object in use. Object is
/QIBM/UserData/OS400/ServiceAgent/trace/esa.log.0.
QSYS.QSRGENSE.QSROBJEC
While I could add these to a BRMS omit list I am wondering, since these
appear to be log files and/or lock indicators, and IMHO appear to be
expendable and something the system will rebuild as needed, if IBM should
perform a CHGATR OBJ('/QIBM/UserData/OS400/ServiceAgent/trace') ATR(*ALWSAV)
VALUE(*NO) IBM has flagged numerous directories like this with that
attribute starting a few releases ago.
IBM Response:
Hi Robert, thank you for contacting the IBM Global support Center. I
discussed with the ESA specialist and he said that The ESA.log.xx files are
trace logs for ESA transmissions and they usually delete them for problem
recreation. Then it is OK if you change the *ALWSAV attribute to *NO.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
<
http://www.dekko.com>
http://www.dekko.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: <mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: <
https://lists.midrange.com/mailman/listinfo/midrange-l>
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: <mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx> MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
<
https://archive.midrange.com/midrange-l>
https://archive.midrange.com/midrange-l.
Please contact <mailto:support@xxxxxxxxxxxxxxxxxxxx> support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
<
https://amazon.midrange.com>
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: <mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: <
https://lists.midrange.com/mailman/listinfo/midrange-l>
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: <mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx> MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at <
https://archive.midrange.com/midrange-l>
https://archive.midrange.com/midrange-l.
Please contact <mailto:support@xxxxxxxxxxxxxxxxxxxx> support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: <
https://amazon.midrange.com>
https://amazon.midrange.com
midrange.com
