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 Oct 30, 2019

OQWT in DSM for Z/OS Query Advisor Enhancement needed

Query Advisor missing obvious SQL predicate datatype inconsistency

While researching a production issue in all our production systems with a remote DB2 program, we ran OQT in DSM and found that the QUERY ADVISOR was missing a very obvious and key SQL problem. A column that is defined with a CHAR datatype was being compared to a literal with NO Quotes that was all numerics. Although the Optimizer will convert it using a CAST function, it avoids the optimal use of an existing index that this column is a part of. We ended up finding it ourselves by looking at the formatted query that the tool created, but it should have showed up as a warning for us to review. I am attaching the full recommendation report that OQWT generated from our BOST production region. We are At DB2 V12 R100 . Running DSM Version 2.1 Release, Build 20190702_1507 . this is the solution that was sent to the developers (this recommendation resulted in a 99% reduction in CPU and I/O):

The SQL in APOIMP18 and APOIMP16 is listed below.

The SQLs in these programs have a WHERE clause coded: AND BATCH_PROC_D = 20191024 BATCH_PROC_D is a character column.

The SQL needs to be coded as AND BATCH_PROC_D = ‘20191024’ (put in quotes)


From IBM support:     Looking for an enhancement to analyze the BEFORE stage query text to detect if there is a CAST function in one side and other side in predicate is a value, then show a warning in our Query Advisor recommendation.


reference CASE TS002923553

Needed by Date Nov 29, 2019
  • Admin
    May Chu
    Oct 9, 2020
    Being evaluated at this time.