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 1, 2025

provide early code update required to be on all queue sharing systems "earlier", via service stream for current release rather than having to order the next release to obtain

It would benefit accounts with shared mq queues to ease upgrades. Today I have to order CBPDO ahead of my z/OS PSI (for 3R1 for instance) to obtain the early code to deploy it through all sysplexes prior to the MQ upgrades that will occur with my PSI. I'm facing the issue again with z/OS 3R2 about to be released. Just after installing RSU2601 (where the MQ early code updates might have been supplied) I will have to initiate an order for the next MQ release and roll the early code with a z/OS toleration release. 

Idea priority High