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).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Provide a PARSE_CL_STMT SQL UDTF that returns parms and values
It would be great to have a way to check CL command options similar to how we do today with PARSE_STATEMENT for SQL statements. The ideal candidate would return the parameters (kwd names) and the value the user passed to those parameter in a table resultSet.
processing CL today we rely on QCMDCHK to syntax check the CL Command but it would be more functional to have a way to parse that CL statement and return the parameters and the value specified. For example: clCmd = 'ADDPFM QGPL/TESTFILE MBR(PICKLES) SRCTYPE(SQL)'
select * from table(qssy2.PARSE_CL_STMT( :clCmd );
Which would return: CMD PARM ORDINAL ELEMS VALUE ADDPFM FILE 1 1 QGPL/TESTFILE ADDPFM MBR 1 1 PICKLES ADDPFM SRCTYPE 1 1 SQL
For parameters with MAX(>1) the ORDINAL would represent each value passed in to the same parameter. While the ELEMS would identify the element value for that ORDINAL of the parameter. For example, a parameter of the following: MYCMD OBJ((QGPL/OBJ1 *FILE) (QGPL/OBJ2 *PGM)) would be returned:
Do not place IBM confidential, company confidential, or personal information into any field.