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
Command prompting control is not executing when no value is entered for a required parameter. Meaning, if a user prompts a command that has a required parameter but then simply presses ENTER instead of filling in the required parameter value, no error message is displayed but all prompting control is also ignored and all parameters are displayed -- including parameters that are normally mutually exclusive of each other.
I opened a PMR for this situation and was told that it is "working as designed" because it is documented that when a required parameter is not supplied then command prompting will display all parameters. Well, I have to tell you that the design is flawed.
It is never "OK" to go ahead and display mutually exclusive parameters. The reason is that it both presents an erroneous (and confusing) display to the user, but it also allows the user to enter data where they shouldn't with no way to programmatically get rid of that data during prompting.
Meaning, once a value is entered into the required field and prompt control *does* execute, prompt control is unable to remove the mutually exclusive parameters from the display because they have values specified in them.
Better, in this case (required fields not filled in), is to not display *any* parameters that have PMTCTL specified. Further, what value is it to allow a PMTCTLPGM to be specified and then NOT call that program so that it can control prompting as it is supposed to be able to do?
In short, prompt control is broken because it does not give the programmer the promised control over command prompting as implied.
There are three ways you can address this issue.
1. Simply change command prompting behavior to not display parameters with PMTCTL specified if required parameters are not supplied.
2. Simply change command prompting behavior to always execute prompt control even if required parameters are not supplied.
3. Add new PMTCTLOVR parameter to the CMD header with options of *NONE (default, for original behavior), *SKIP (don't display parameters with PMTCTL if required fields are not supplied), and *ALWAYS (execute PMTCTL even if required fields are not supplied) to make all three behaviors possible.
The following two source members (slightly modified from the example given in the IBM manual) demonstrate the problem.
Do not place IBM confidential, company confidential, or personal information into any field.