This is an IBM Automation portal for Integration products. 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
Provide a AUTHOREV(NODISPLAY) option similar to CMDEV(NODISPLAY) to avoid 1000's of generated monitoring events that are no real authorization issue when using IBM MQ Explorer.
When using MQ Explorer, you get to see the queues / alias queues / ... for which you're authorized. When AUTHOREV is enabled, listing the queues in MQ Explorer generates 1000's of event messages on SYSTEM.ADMIN.QMGR.EVENT (depending on the number of queues of course) indicating that the user is not authorized. The number of messages generated, and the reason why, is so intrusive that the alternative at the moment is to disable AUTHOREV. Disabling AUTHOREV of course has the consequence that we also miss real authorization issues. User X trying to put / get messages on a queue that he's not supposed to use.
Using a filter in MQ Explorer reduces the number of messages, but not all. And, for the user (developer) that uses MQ Explorer there is no added value. The MQ admin also can't force developers to use filters in MQ Explorer...
Similar to the option available with CMDEV, the option NODISPLAY for AUTHOREV would solve this. Don't generate monitoring events for DISPLAY & INQUIRE attempts. This would allow us to profit from event monitoring concerning real authorization issues without the many messages when using MQ Explorer.
Do not place IBM confidential, company confidential, or personal information into any field.