× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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 <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Monday, May 11, 2020 9:06 AM
To: Midrange Systems Technical Discussion <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


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

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

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.