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 Not under consideration
Created by Guest
Created on Sep 19, 2018

Provide detail reason(s) for objects determined by QM to have insufficient data for smarter reorg recommendations RFE 124993

A more detailed explanation is needed in the output of the Automation Tool job profile build job for any object that is processed by QM as part of smarter reorg recommendations and returns an ‘Insufficient data' condition.    Currently, QM has to check each of the possible data thresholds for sufficient data anyway, so it knows the exact check(s) that fail, and should therefore return one or more detail reasons to the user in the job profile build job output.  This would greatly help the user understand why an object did not meet the sufficient data threshold(s), so that the thresholds can be adjusted appropriately.

Use Case
Many objects that are selected for reorg by the base reorg criteria defined in the Automation Tool and are passed to Db2 Query Monitor for analysis are rejected by QM due to insufficient data.  There are several possible reasons for this, and the DBA currently has no way to determine which threshold check(s) failed.  It would greatly help the DBA to understand why the insufficient data result is being flagged for an object.
  • Admin
    May Chu
    Apr 6, 2021

    Thank you for submitting this enhancement request. While we view all the enhancement requests we receive as valuable and we would like to implement all of them, in an effort to have maximum transparency we are closing the ones that don’t currently appear on our two year product roadmap. This is not to say that these enhancements may not still be implemented at some point in the future, as we constantly evaluate our requirements on the basis of customer demand and technical impact and try to deliver maximum value to our customers. We appreciate your feedback and would be happy to discuss your enhancement requests further