This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 updateson them if they matter to you. If you can't find what you are looking for,
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.