Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Mar 26, 2019

sql describe for embedded SELECT (embedded in CREATE or INSERT)

I work into a security software, and I have to identify when sensitive data are read
RCAC is not always the solution.
For example : when sensitive data are worked from a well known program, it is ok,
But when the same data are worked from STRSQL or ACS sql script, it is not.
And we have customers still in V7.1 (RCAC appears in V7.2)

I know some IBM customers uses sql describe and detect it is not a select because describe returns nothing.
I propose an extention of the syntax :

Use Case:

when the statement I work with is, for example,

Create table qtemp/test as ( select * from qiws.qcustcdt)with data
Table TEST created in QTEMP.

It is obvious there is a select in this statement (not only a select, but a there is an embedded select)
And it is also obvious that the data are duplicated.

Idea priority Urgent
  • Guest
    Feb 13, 2021

    IBM does not intend to provide the solution described by this request at this time, so it is being closed.

    We believe there is an existing solution that might work just as well, if not better, than the proposed enhancement in this RFE request.

    The table function QSYS2.PARSE_STATEMENT can be passed an SQL statement. It returns the type of SQL statement and a list of the object names that are found in the statement. This includes not just table names, but column names and function names as well.

  • Guest
    Mar 27, 2019

    Agree. 7.1 is out of support so any changes would be made to 7.2 and 7.3 only. And, with 7.4 just around the corner, the days of getting major enhancements to 7.2 are going to come to an end. If the current trend continues IBM will support the current release and one level back only. Personally I agree with this as customers tend to be slower to upgrade, but eventually, they need to. You can't keep supporting years and years of OS releases.


  • Guest
    Mar 27, 2019

    V7R1 is already End-Of-Support since April 30 2018 so even if your proposal would make it... it will never be available at V7R1.

    You can't advocate security and run on an unsupported release !