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

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.


Add a new idea Subscribe
Status Not under consideration
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Feb 16, 2022

RELATED IDEAS

Allow IMS applications to connect with the MQ queue sharing group name

Allow a IMS BMP to issue an MQCONN call specifying the queue sharing group name instead of the queue manager name.

We have a queue sharing group running over multiple systems with a queue manager on each of those systems. The BMP can run on any system. We want the BMP application to be able to specify the queue sharing group name on the MQCONN call, rather than having to know and specify the queue manager name for the system it is currently running on for the MQCONN call.

It is cumbersome for the application to be coded to know which system it is running on and then translate that to a queue manager name for that system.

This was previously requested in the IBM RFE community and they responded:-


https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=149936

"After reviewing this request for enhancement with the MQ product team, we concluded that the key enhancement needed for this requirement would be required in the MQ product. Therefore, we kindly ask you to open a new idea for the MQ product in the Integration customer portal - https://integration-development.ideas.ibm.com"



Idea priority Low
  • Admin
    Mark Taylor
    Reply
    |     Mar 22, 2022

    We recognise that this is a reasonable requirement. However it doesn't fit with our delivery plans for the next couple of years.

    As a result we are declining this Idea.

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.