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 Jun 14, 2024

Multi-instance MQ be able of switchover without intervention after a failover

Problema: having 2 mq multi-instances, one as primary and the other as secondary and running in standby mode. When the primary MQ fails, the other one takes over as primary. However, the previous one goes to the status of “running elsewhere” and needs a new start to have a high availability environment again in case of a new failure. This scenario doesn't permit a new switchover without human intervention.

I ask for a changing in the MQ product to activate automatically the MQ with the status  "running elsewhere" after a switchover.


Idea priority High
  • Admin
    Mark Taylor
    Jun 25, 2024

    This is not something that we would put into MQ itself - it would require something "outside" the queue manager such as an independent agent that would itself require managing.

    It ought to be integrated into whatever mechanism that you are using to start the queue manager in the first place. For example, systemd could be configured to restart failed instances automatically.

  • Guest
    Jun 18, 2024

    The secondary MQ should be "running as standby" always