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 Future consideration
Created by Guest
Created on Mar 18, 2015

Provide AMQSCLMA as native functionality

Headline is self explanatory. Instead of having to deploy a helper application, which requires preparation, like defining a queue to which replies from command server will be put, for each of its instances, etc, this should be implemented natively, with additional local queue attributes that control this functionality, one that defines if queue is a subject to this control (because consumers are long running always connected), another for poll interval of the monitoring, etc.
Besides that, setting this parameters for one queue instance in a cluster should propagate throughout the cluster, because there is no need for this attributes to be different between instances of the same cluster queue.

Idea priority Medium
RFE ID 68216
RFE Product IBM MQ
  • 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
    Mar 20, 2015

    Whether consumers are long running always connected or not, can be automatically detected, so probably there is no need to indicate that manually.