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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
In the IBM update that indicated this enhancement was delivered, that actual deliverable was not described.
There is is a way to return a list of objects referenced by static SQL statements embedded in a program or service program.
The QSYS2.SYSPROGRAMSTMTSTAT view returns one row for every static SQL statement in every program or service program.
The QSYS2.PARSE_STATEMENT table function takes an SQL statement as input and returns a list of the objects it finds in the statement.
Combine these two services and you can get a list of every object referenced by every static SQL statement.
Note that there is another RFE for a DSPPGMREF service. It is the RFE IBM is using for consideration of an SQL service that would be a more complete match for the information returned by the CL command.
From Sql i would expect to have not only the table names in a pgm, but also the columns used in the PGM.
What about SQL are you thinking is the same as *PGM objects? Triggers, functions or procedures? Many SQL procedure language objects like the above create system objects that can be cross referenced using DSPPGMREF. These typically generate a CLE *SRVPGM object.