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
When you create a message queue watch, the OS spawns a QSCWCHPS job whenever the specified message ID is generated. That QSCWCHPS job determines if it's for the specified message queue and, if it is, executes the watch program. This causes a tremendous amount of unnecessary overhead when you only want to monitor a single message queue. The QSCWCHPS job should not be spawned unless the new message was in the correct message queue.
I specified a message queue and *ALL for the message ID. That spawned so many QSCWCHPS jobs that the audit journal consumed 10% of my total DASD in a single day. Not to mention the wasted CPU cycles.
We're using an exit point security package that sends a message to a specified message queue when a violation occurs. We need to immediately handle those messages. I need to create a watch to watch for any new message added to that message queue.
Do not place IBM confidential, company confidential, or personal information into any field.