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 Jul 28, 2020

Report all SQL calls in native stored procedures in Query Monitor

See case# TS003954339. Sometimes Query monitor doesn't capture the SQL statement but gives the message: CQM145I - SQL TEXT NOT AVAILABLE, instead. IBM case states that these are internal SQL calls in native stored procedures. In my case they were the second highest consumer of elapsed time and I was unable to troubleshoot the problem further.

Needed by Date Aug 17, 2020
  • Admin
    May Chu
    Aug 5, 2020

    The proposed solution could be:

    1. Introduce a new message that identifies the ‘statement’ as Native Stored Procedure non-object related, procedural statements.

    2. Modify QM to report the internal CREATE PROCEDURE as the text which is the text that is stored in TEXT column of the SYSROUTINES catalog table and to identify the call in summaries ,etc. as dynamic.