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 Not under consideration
Created by Guest
Created on Sep 12, 2012

WMQ Support for MSCS Majority Node Cluster

Please see below which is a previous response to a RFE – we are basically following up this original query and trying to determine if/when support will be available for WMQ using MSCS Majority Node cluster. When queried last time we were told it was planned to be looked at for a future release (as can be seen from the email below).

---------------------------------
Subject: MQSeries Requirements Response for R5495: WebSphere MQ Support for ‘Majority Node Set Cluster'

Thank you for submitting an MQSeries Requirement.

We have reviewed your requirement and have the following
response:

Recognised- IBM agrees with the request and a solution appears to be a desirable objective. A solution, however, may not presently appear feasible or implementable. No IBM commitment is made or implied as to the eventual delivery of an acceptable solution.


Thank you for raising this request.

Presently WMQ is not tested on MSCS Majority Node Set Cluster. Although the change (from single disk quorum to multi disk quorum) is on MSCS front, we are unable to confirm if WMQ will work as is. It requires a good amount of testing to determine if any change is required from WMQ side also.

We plan to take this up in our future releases.
Please quote reference number: R5495

Idea priority High
RFE ID 26424
RFE URL
RFE Product IBM MQ
  • Guest
    Jan 11, 2022
    While we know no reason why this should not work, it is not likely to be explicitly tested and therefore mentioned in the supported configurations.

    Therefore this idea is being declined.

  • 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
    Oct 15, 2012

    It is our intention to support MSCS Majority Node Set Cluster , we are at present unable to give a timeline for this, please see the following text:

    IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.