Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Apr 3, 2013

Additional MQSC command (for full Repository qmgrs) to list queue/qmgr subscribers

In a large MQ cluster , its possible that a specific cluster queue has been subscribed to by many "client" qmgrs in the cluster. To determine the impact of a specific queue being unavailable (eg the consuming application has failed) , there is currently no quick method of determining which client qmgrs in the cluster have subscribed to this queue so that the true business impact of the application failure can be determined. I would like to see a new MQSC command that could be issued on a full repository qmgr, that will take a published cluster object (queue or qmgr) as a parameter, and then produce a list of all the qmgrs that have 'registered an interest' in this object. Currently the only way to gather this data would be to interrogate all the Partial repository qmgrs in the cluster using a DISPLAY CLUSQMGR or DISPLAY QC command , then consolidate/parse the command output . The same information is contained within the full repository for the cluster so it would be logical to issue a single command at the 'source' to collect the data.

Idea priority Low
RFE ID 33160
RFE Product IBM MQ
  • Guest
    Jan 7, 2022

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

    As a result we are declining this Idea. While declined the Idea can still be voted, and commented, upon.

  • Guest
    Oct 15, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM MQ

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM MQ

  • Guest
    Feb 13, 2014

    The concept of showing which queue managers know about specific queues will be considered for a future version of MQ.

    The suggested extension to show task information is not something that would be done. That information does not flow around the cluster; nor should it.