This is the public portal for all IBM Z Hardware and Operating System related offerings. 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
We suggest using IRRXUTIL if you would like to filter this information.
This requirement has been accepted as an uncommitted candidate. Thanks.
Hi Robert - yes, I am not thinking in modifying the SETROPTS LIST but instead, preventing users to try a different command like the one I mentioned when there was an attempt to filter the active classes. If there isn't a way to filter, RACF couldn't just accept a command like SETROPTS CLASSACT(*) LIST as the list in this case would be part of an unique command and it doesn't go right after the SETROPTS. I am interested in seeing more comments about what I just wrote so we can think together in a way to close this vulnerability.
Thanks,
Lucas.
Whereas I disagree with modifying SETROPTS LIST to allow listing subsets of its information, I do think SETROPTS should not accept and process CLASSACT(*) given that inadvertent activation of Default Return Code 8 classes could be very disruptive. SETROPTS should require classes to be individually named in CLASSACT.