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
No good way to specify a variable with list parameters.
Transferred from AD0276 -
Since the early days of the CPF operating system on the System/38, We've been bedeviled by specifying variables for list parameters in CL programs. For every other parameter on the system, if you need to specify a variable you're good to go, but there has never been a good way to specify a variable with list parameters. If you specify one list element you're OK, but that's rarely what is needed. Often times one needs to specify multiple list elements and you can never be sure how many will be needed at execution time. The current design of the command processing environment makes this difficult.
Current workaround: The standard work-around for this problem has always been to create a CL command in a variable and then execute it with a command execution API like QCMDEXC, but there are inherent problems (see “impact” above).
Proposed resolution: The solution combines with requirements #212 (Arrays in CL) and #215 (Qualified Data Structures in CL), and it proposes to change the command environment to allow arrays and data structure arrays to be specified in list parameters. This will eliminate the “impact” issues by giving the CL command environment a discrete set of data elements. Full details and illustrations can be found at this URL on the System i News iDigress blog: http://www.systeminetwork.com/blog/idigress-23/rpg-programming/solving-problem-list-parameters-variables-cl-699271
Do not place IBM confidential, company confidential, or personal information into any field.