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
In addition to adopting authority to access data BRMS should swap user profiles too.
IBM i 7.5 killed some BRMS functions we were using by changing the *PUBLIC authority to data from *USE to *EXCLUDE. You may think this is a security enhancement but it isn't. Now instead of users only being able to see data we have to add QBRMS as a group or supplemental group which then allows them to update and delete data too.
The reason we had to do this is outlined in case TS010745419. Basically when a user is using the BRMS network feature and it access data on a remote system it started failing at IBM i 7.5 because of the authority change outlined with: "The default for the BRMS shipped database is changing from *PUBLIC *USE authority to *PUBLIC *EXCLUDE." at https://www.ibm.com/docs/en/i/7.5?topic=programs-backup-recovery-media-services-5770-br1
I feel that if the programs not only used adopted authority but also used profile switching then they would still be accessing the data as QBRMS and we wouldn't have to assign the QBRMS group profile to uses thus giving them elevated access to the data outside of the BRMS programs.
Do not place IBM confidential, company confidential, or personal information into any field.