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 Delivered
Created by Guest
Created on Jan 29, 2019

As MQ Cluster Queue out of date design, if it can become as severity level FDC or alart in MQ desgin

Request:As MQ Cluster Queue out of date design, if it can become as severity level FDC or alart in MQ desgin.

Why:Many user suffer their critical system and impact business large, event the MQ Log had record but not enough.

Idea priority Urgent
RFE ID 129437
RFE URL
RFE Product IBM MQ
  • Guest
    Reply
    |
    Dec 15, 2023
    Various diagnostic improvements made over several releases
  • Guest
    Reply
    |
    Aug 27, 2020

    FDCs are primarily intended to provide diagnostic information to MQ support in the event of a product failure being detected, and should not be relied on by users to detect configuration or system errors. There are a number of reasons updates for cluster objects may not be received, and by design the product only issues FDCs when it appears that the reason for out of date information is an internal failure (rather than for example a network issue).

    However, in many cases where there is no product 'failure', administrator action is still required (for example to restart a channel), and therefore an informational message as provided today is not necessarily appropriate. Development will review generated messages to ensure that appropriate severities are assigned to the messages and can therefore be appropriately monitored. Use of 'log targets' may assist in automatic monitoring for these alerts.