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 Feb 16, 2026

Capability to backout MQ CD releases / maintenance z/OS

In our regulated environment, it is not acceptable to adopt a 'fix forward' approach if maintenance or patches applied to infrastructure software such as MQ cause issues for our applications.

As a pre-requisite to obtaining internal approval to apply any software change, we need to demonstrate the capability to back out the work in case it causes an unexpected change in application behaviour (even if the ultimate resolution does not involve a change to IBM code). 

We would like to explore the MQ CD delivery model, but the inability to back off MQ CD software maintenance means it is not possible for us to do so.  Because a CD queue manager cannot be reverted to an earlier release level without rebuilding (cold starting) the queue manager, it becomes impractical to test that as a backout approach in our development environments, let alone obtain signoff to adopt such a method as a backout plan in production.

Please consider allowing reversion of fixes/maintenance on an MQ CD queue manager so that backout of an upgrade activity can be undertaken without having to cold start the queue manager. It would be acceptable to restrict the scope of the backout activity (for example, only allowing reversion by one level)

Idea priority Low