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).
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.
See this idea on ideas.ibm.com
With the current IGQ implementation, IGQ does not scale well in a QSG ( Queue-Sharing Group ) and Coupling-Facility setup.
MQ Development has mentioned that there is a need to look at splitting up the IGQ (i.e. have one per qmgr, or maybe even one per source/target qmgr combination) so that the getting task can do gets without match options.
With the current implementation, MQGETS done with 'Match' options severely puts a strain on the CPU and I/O, as it needs to contend with not only a Primary key, but also a Secondary key, thereby causing significant delays.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
This is not something that can be done in just MQ - it would require changes in other products or components such as the CF. As such, this is not likely to be achieveable in the next couple of years. Therefore this request is being declined.