This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.