Integration
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 updates on 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
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.
This idea would also solve the following scenario:
- Clients connect to SVRCONN channels (QSGDISP of GROUP, or multiple with QSGDISP of QMGR) across the queue sharing group.
- Using Sysplex Distributor for this, we can maintain a balance at the queue manager level using, for example, the SERVERWLM distribution method.
- When multiple clients (using different SVRCONN channels) share the same Sysplex Distributor definition, a client application (App A) may be skewed across the QSG based on connections from other clients (App [B-Z]) being established in between connections made by the App A client. In the worst case scenario, based on timing, this may mean one client may be connected only to one or two members in the QSG and not benefit from the balance provided by Sysplex Distributor until they reconnect to the QSG.
By moving the connection logic from the client to the queue manager, MQ can better manage the distribution of client connections on a channel by channel basis, eliminating the need for individual Sysplex Distributor definitions for each application. This simplifies configuration, reduces delivery time when new clients are onboarded, and reduces the likeliness of client connection imbalance across the QSG for shared Sysplex Distributor definitions.
In addition to this use case, we would also benefit from connection rebalance after a queue manager cycle, mentioned above, to prevent connections concentrating on queue managers that are not brought down for maintenance or brought up first in a rolling recycle / all down & up while other CHINITs are yet to become available for connections.
We recognize that this is a valid requirement, and in fact is a good idea. However it doesn't fit with our delivery plans for the next year or so.
As a result we are declining this idea. While declined the idea can still be voted, and commented, upon. We will retain this idea on our internal backlog for future consideration.
It would be useful to understand if there are other customers who are also interested in this. If you are, please vote!
I fully agreed!