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

Add exclude filtering in the Snapshot History function

We're experiencing a problem as described in case TS007930116 in which we're unable to see data from all Db2 members in the thread history. In testing we found that by limiting the number of threads thru use of the collection filter (in our test we limited by PLAN=DISTSERV), we can see data from all members. Unfortunately, about 2/3 of our threads are idle threads and at present there is no method of eliminating these threads from the thread history display. IBM has suggested the following solution to resolve this issue:

"The cleanest way to address the problem is to to enhance the product to allow for 'exclude filtering' in the Snapshot History function. This should allow for excluding Plans with an empty name (mostly for idle threads that make up a large part of the customer threads) or other identifiers supported by the Db2 WQAL filtering (details to be specified). This will also improve the footprint as less data will be retrieved from Db2 in the first place and subsequently less data is stored in the Snapshot history data store."

We agree with this proposed solution and look forward to its implementation.

Thank you,


Needed By Quarter