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:
Post your ideas
Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas and add comments to ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Specific link you will want to bookmark for future use
IBM Unified Ideas Portal-https://ideas.ibm.com/- Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.
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.