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:

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:

Status Future consideration
Workspace Db2 AI for z/OS
Created by Guest
Created on Dec 19, 2017

Give the option to make an index "invisible" to DB2

Sometimes, when I have added and index, I have had some surprises in the optimizer using that index when it should not. I would like a quick way to make the index "invisible" to the optimizer and make it not eligible for access paths until I specify for that to happen. It would be much quicker to "flip a switch" than to drop the index (and then have to rebuild it once again to have it used).
  • Guest
    Jan 15, 2020

    This would definitely help DBAs during program optimization, but I find even more important that:

    • it would prevent -904 errors during the create process (24x7 dynamic sql vs the time needed for rebuilding large indexes)
    • it would improve DevOpt process (takes off the risk of access path changes when nobody is watching, just because new indexes are created; we tend to avoid creating indexes as automated tasks because of this)