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 Jul 31, 2026

IBM MQ administrators need a non-disruptive way to make CLUSRCVR SSLCIPH changes.

IBM MQ administrators need a non-disruptive way to make CLUSRCVR SSLCIPH changes. Currently, if an IBM MQ administrator changes the SSLCIPH on a CLUSRCVR channel (ex. ALTER CHL(MY.CHL) CHLTYPE(CLUSRCVR) SSLCIPH(ANY_TLS13_OR_HIGHER)), there is the possibility that IBM MQ clustering will not properly propagate that change to all the partial repositories. This is recognized in the IBM MQ manual, and the documented fix for this is for the IBM MQ administrator to run a command like REFRESH CLUSTER(MYCLUS) or REFRESH CLUSTER(MYCLUS) REPOS(YES) on the partial repository that did not get the SSLCIPH update. However, this REFRESH CLUSTER can be disruptive to running applications (ex. apps can receive a 2085 during a REFRESH CLUSTER), and the IBM MQ administrators need another way to get the partial repository to receive the SSLCIPH update with out having to run a potentially disruptive REFRESH CLUSTER command. Perhaps one option is a new REFRESH CLUSTER CHL command, that is more targeted and can hopefully be non-disruptive. Regardless, there is the need for IBM MQ administrators to be able to make ALTER CHL(MY.CHL) CHLTYPE(CLUSRCVR) SSLCIPH(ANY_TLS13_OR_HIGHER)) configuration changes in a way that is non-disruptive to the IBM MQ environment.

Idea priority High