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 Not under consideration
Created by Guest
Created on Dec 5, 2019

Filter out "db2inst1" user's short query statements in "Database Responsiveness" in Web console

One customer has an enhancement requirement in Web console in IIAS so they can filter out "db2inst1" user's short query statements in "Database Responsiveness" in Web console . They want to focus on user SQLs only.  Currently "QUERY EXECUTIONS" has "filter" menu to exclude specific database users' query executions but "Database Responsiveness" window does not. In this case, SQLs under db2inst1 database user are short running and most are not related to actual customer applications. So they want to exclude all those short SQL executions from db2inst1 user.

Needed by Date Dec 31, 2019
  • Guest
    Feb 10, 2020

    Could you comment any? I think it has not been checked yet.