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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Created by Guest
Created on Jun 23, 2021

Add support for static SQL queries text storage in CQM_SUMM_TEXT

There is currently no support for the static SQL in CQM when one wants to store the SQLTEXT for such queries. Only dynamic SQL is supported. It is currently possible to see in the ISPF interface the static sql, but it is gone after a rollup of the backend temp datasets and this data is not offloaded into tables ei. CQM_SUMM_TEXT, like uit is done for dynamic SQL. Only a statement number is stored. However, this presents an obvious challange when there is a need to look at the historical data of query processing and object usage and in the meantime, the package used to execute the static SQL was already rebound, freed etc. It is often true in dynamically changing environment that programs are modified, DBRMs are newly created and packages are boud, old are freed, some are replaced. When only a stmt number is stored, it is not possible to analyze static usage of objects which can lead to invalid assumptions.

Proposed solution:

It should be a part of the process, to extract sql complete text from catalog tables for every static sql executed based on the statement number, statement ID, package name etc and externalized it to the backup tables that are used to store the CQM historical data. In this case for example CQM_SUMM_TEXT. This should be done immediatelly when such query is executed and stored in temporrary files, as it is done for dynamic queries. It seems to be low effort change, since the complete machanism of storing and saving this information is already in place for dynamic sql, only an extra step to extract the SQLTEXT from catalog is needed.

Thanks to this enhancement, CQM will be able to provide a much more comprehansive and complete picture of queries executed, objects used etc in DB2 and will allow for extensive historical analysis which is often vital in every DB2 shop.

Needed By Yesterday (Let's go already!)
  • Admin
    May Chu
    Aug 13, 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