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 Oct 3, 2013

Message Reallocation Enhancement

When messages are not able to be delivered through cluster channels to a destination which is unreachable MQ will attempt message reallocation to redirect the messages. We understand from PMR 16826 082 000 that 3 gets and 1 put will occur for each message in this state. The CPU used by the CHIN at this point is very high and the ability to do other work on the LPAR is low. We would like to see an ability to disable this feature when it is know that all backend destination have become unreachable. IBM suggested that we stop mode force the cluster SDR channels, and with all the autodefined channels and the lack of CPU when this situation arises that process did not work. In addition we would prefer to see the processing continue once a destination became available. This is only an issue when all of the backends are down.

Idea priority High
RFE ID 39891
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
    Sep 1, 2014

    We are considering further optimisations for how and when messages are reallocated for future versions of MQ.