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
Created by Guest
Created on Mar 14, 2022

Generic Ignore for New v12 Columns on SYSTABLESPACE and SYSINDEX

v12 introduced additional columns on SYSTABLESPACE and SYSINDEX which match attributes that were previously present on SYSTABLEPART and SYSINDEXPART, respectively. When a source object has been created in v12 is compared to a target object which was created prior to v12, Object Compare currently generates an ALTER on the target tablespace or index. We have set up ignores to stifle this behavior, but then if there is a legitimate change to an attribute on the source which we want to be applied to the target, the actual change to the attribute is also ignored (in this case, it would be a difference on SYSTABLEPART, also). We would like to see an option to ignore these new v12 columns so that if the only reason there is a difference is because the source was created in v12 or after and the target was created prior to v12, it will be ignored, but if there is an actual change to an attribute, it would still generate WSL to apply the change to the target as well.

Needed By Yesterday (Let's go already!)