Skip to Main Content
IBM Power Ideas Portal

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 (

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace IBM i
Created by Guest
Created on May 13, 2018


When specify PARM of *CMD source, you can specify the PMTCTL keyword to enable conditional prompting of that PARM.
The current permissible values are: Name, *NONE and *PMTCTL
We would like to have an additional *NEVER (or any other name of your liking) to disable prompting of that PARM

Use Case:

I have 2 commands that are almost identical.
95% of the parameters are joined.
There are few parameters added to one command that are not needed in the other and vice versa.
I would like to have single CMD source code for both as well as 1 CPP code.
For the parameters that are extra for each command, they should not be able to prompt on the other command, although they still exist in the CMD code and be passed to the CPP.
Before compiling, we will copy the single source to another name, alter it a bit (by an automated program of course) and compile it in the 2 codes so I'll end up with 2 commands.
For example, we can alter a PARM at the top of the source that is CONSTANT(<utility name>) so the CPP will know which command it serves now.

But it looks like there is no way to "hide" the unwanted PARM's in one command while showing the wanted, and vice versa on the other command.
The PMTCTL just wouldn't allow us to use a PARM that defined as CONSTANT to be used for PMTCTL CTL.

If we will have a PMTCTL(*NEVER) in the PARM, or alternatively PMTCTL CTL(*NEVER), we can alter the source code that we copy and switch between the wanted PMTCTL(*NONE or *NEVER).
If the PMTCTL command is modified (rather than the PARM command), than maybe CTL can be *NEVER and *ALWAYS to make it easier switching.

Idea priority Low
  • Guest
    Apr 16, 2020

    IBM has determined that this change is very specific and does not provide broad value to the user community.