Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Workspace Db2
Created by Guest
Created on Dec 29, 2020

DB2Z-Allow for EXCHANGE DATA function on Clone table to NOT put packages in VALID status of 'A'

We have processes that use the clone table feature to allow for non disruptive load operations. When we do the exchange data the packages on the primary table move to a VALID STATUS of 'A' when they had a status of 'Y' previously. This creates issues for us when changes are made to the table such as migrating to PBG from segmented. Packages can then go invalid and will no longer rebind. We need the status of VALID to remain 'Y'. I would expect lots of customers are impacted by this but they are not aware unless they monitor their package status.

Needed by Date Feb 1, 2021