Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Jun 6, 2025

Trim blanks from 60 byte statement text in IFCID 316

IFCID 316 contains only the first 60 bytes of the SQL text. Some programs may, for readability, include lots of blank spaces around SQL text. In extreme cases (python scripts) the text is preceded by a line of blanks. In these cases the 60 bytes of SQL text in IFCID 316 will contain nothing but blanks. Other times, the 60 bytes may contain SELECT and nothing else since the next part of the text is on another line. Since there are only 60 bytes to work with, try to get as much relevant information in there.

Needed By Quarter
  • Admin
    Janet Figone
    Nov 22, 2025

    Hello Thomas, Thanks for submitting this enhancement request. We have not received the additional information requested, so unfortunately, we have closed this idea. If you would like to pursue this enhancement, please create a new Aha! idea and provide the details, including the requested information, and submit it. We will continue to review it at that point.

    Sincerely,

    Db2 for z/OS team

  • Admin
    Janet Figone
    Oct 31, 2025

    Hello Thomas, Thank you for submitting this enhancement request. Development has reviewed it and is still in of some additional context from you based on the following:

    IFCID 316 can be returned using IFI READS which returns all the statements in the dynamic statement cache (DSC). IFCID 316 is also produced when SQL is removed from (or pushed out of) the DSC. Can you let us know which which is causing the pain?

    For IFI READS, you can follow up with another IFI READS call using IFCID 317 for a specific stmt id or you can issue EXPLAIN STMTCACHE ALL. Assuming the SQL is still in the cache, you should get the entire sql text. If this is your situation, and those 2 solutions are not adequate, please provide information on why it is inadequate and our team will adjust this idea to fit your requirement.

    For push out, there is an existing idea: DB24ZOS-I-791 This idea is to issue ifcid 317 with ifcid 316 when sql is pushed out of the cache so that the user can see the entire sql text. If that is your situation, we encourage you to vote for it.

    Sincerely,

    The Db2 for z/OS team

  • Admin
    Janet Figone
    Jul 16, 2025

    Hello Thomas, Thank you for submitting this enhancement request. Development has reviewed it needs some additional context from you based on the following:

    IFCID 316 can be returned using IFI READS which returns all the statements in the dynamic statement cache (DSC). IFCID 316 is also produced when SQL is removed from (or pushed out of) the DSC. Can you let us know which which is causing the pain?

    For IFI READS, you can follow up with another IFI READS call using IFCID 317 for a specific stmt id or you can issue EXPLAIN STMTCACHE ALL. Assuming the SQL is still in the cache, you should get the entire sql text. If this is your situation, and those 2 solutions are not adequate, please provide information on why it is inadequate and our team will adjust this idea to fit your requirement.

    For push out, there is an existing idea: DB24ZOS-I-791 This idea is to issue ifcid 317 with ifcid 316 when sql is pushed out of the cache so that the user can see the entire sql text. If that is your situation, we encourage you to vote for it.

    Sincerely,

    The Db2 for z/OS team