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 Functionality already exists
Created by Guest
Created on Oct 28, 2020

Specify Application Trace

Customer is complaining that he is unable to perform traces on DB2 threads coming from the distributed side. These threads arrive all to DB2 with the same plan name ('DISTSERV'), and the only way to tell them apart is to use the Correlation ID (CORRID field). Unfortunately, panel KD2PSAP (Specify Application Trace Collection) is somewhat limited when it comes to this issue. This panel doesn't allow the selection of threads by their CORRID. Although Omegamon is able to show the CORRID, it won't allow it to be used as a filter, which is extremely limiting for the customer. Customer would like to get some suggestions on how to overcome this limitations. These traces are extremely important for the customer, and the OEM monitor that customer is currently trying to replace allows these traces to be taken.