This portal is to open public enhancement requests against IBM Z Software products. 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.
We have been evaluating this some more, and we think there should be an optional 4th argument that would be an integer that would be set to the number of array elements assigned (and this would be useful even if this was the last argument since the source may not have as many array elements as the target even without a selector). Then we would have the selector, and we have 2 proposals for that:
1) the selector is specified via 3 arguments: the name of a field, e.g. "TRAINING", an operator (EQ,NE,GT,etc), and a value to be tested for, e.g. "Y"
or
2) the selector is specified via one argument that is a function you write, that gets the name of an element we are about to assign to (so, "NAME", "ELEV" or TRAINING" in your example) and the value (as a string) that is about to be assigned to it (so, "MATHER", 12000, "Y", etc in your example). The function then returns 0 or 1 indicating if the selection should be made or not.
option 1) is simpler and faster, but 2) offers more flexibility (for example, you could select for a range of values with it)
I suppose, being PL/I, we could offer both 1) and 2) and let you choose which to use for various cases
But do you have comments or preferencs?
1) the selector is specified via 3 arguments: the name of a field, e.g. "TRAINING", an operator (EQ,NE,GT,etc), and a value to be tested for, e.g. "Y"
or
2) the selector is specified via one argument that is a function you write, that gets the name of an element we are about to assign to (so, "NAME", "ELEV" or TRAINING" in your example) and the value (as a string) that is about to be assigned to it (so, "MATHER", 12000, "Y", etc in your example). The function then returns 0 or 1 indicating if the selection should be made or not.
option 1) is simpler and faster, but 2) offers more flexibility (for example, you could select for a range of values with it)
I suppose, being PL/I, we could offer both 1) and 2) and let you choose which to use for various cases
But do you have comments or preferencs?