Skip to Main Content
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.


Status Under review
Created by Guest
Created on May 25, 2026

MQ Web Console - show full list of cluster queue managers and identify suspended ones

Use case / problem
We run IBM MQ 9.4 on OpenShift containers with the MQ Web Console enabled. From Manage -> Queue Manager -> MQ Network the console tells us a cluster's name, total queue manager count, suspended count, and health summary - but it does not list which queue managers are members of the cluster, nor which specific QM(s) are in a suspended state. To answer those two basic operational questions we have to drop into the queue manager pod and run DISPLAY CLUSQMGR(*) via runmqsc, which defeats the purpose of having a web console for cluster operations and observability.

Current behaviour
- Cluster summary shows: cluster name, member count, suspended count, health badge.
- No way to expand the cluster card to view the participating queue managers.
- No way to identify which queue manager(s) are suspended (only a count).

Proposed enhancement
1. In the cluster panel, allow drill-down to a list of cluster queue managers (equivalent to DISPLAY CLUSQMGR(*)) showing name, QMID, channel name, channel state, suspended status, full repository flag, and last-seen timestamp.
2. Surface a clear indicator (icon/badge) against any cluster QM that is suspended (SUSPEND QMGR CLUSTER(...)), so operators can immediately identify which member needs attention.
3. Optionally allow filtering/sorting by suspended state, channel state, or full-repo role.

Value
- Removes the need for SRE/operators to exec into QM pods just to inventory a cluster or find a suspended member.
- Brings the Web Console to parity with the operational visibility that runmqsc already provides.
- Improves incident response time (suspended QMs are a common root cause investigation).
- Aligns with the container/Kubernetes operating model where direct pod access is increasingly restricted.

Idea priority Medium