Skip to Main Content
IBM Power 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:

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,

  1. Post an idea

  2. Upvote ideas and add comments to ideas that matter most to you

  3. 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.

Status Not under consideration
Workspace IBM i
Created by Guest
Created on Feb 11, 2022

Provide a CL Command Parameter Option for Required when INTERACTIVE

some CL command parameters can be designated as MIN(1) which makes them have a value before the command may be run.
We need a way to set parameters to REQUIRED when they are run interactively vs batch.
Add a RQD parameter (or similar) to PARM statements in CMD definition source so that RQD(*INTERACT) could be used to override the other parameters settings (such as MIN(1) when run interactively vs batch.
See Use Case for example.


Use Case:

As an example: The IBM RSTOBJ command has a RSTLIB parameter. By default that parameter is RSTLIB(*SAVLIB). Which is fine. However, when run interactively, we want the end-user to be required to enter an explicit value for RSTLIB so they don't accidentally overlay existing production data.
If there were an option of RQD(*INTERACT) on the PARM/ELEM/QUAL statements that behaved like MIN(1) when Interactive and like MIN(0) when not interactive that would be great.
This should also be an option on CHGCMDDFT so we can change existing command parameters.


Idea priority Low
  • Guest
    Mar 10, 2022

    Okay. Then we need to think of another approach for this situation where a parameter is required but could also have a default when not interactive.
    Mostly this will apply to IBM-supplied commands. Perhaps something like you did with ENDTCPSVR where the first parm had defaulted to *ALL and after a Release two you realized it wasn't the best idea. So you add the infamous "Are you sure" prompt. I wouldn't mind having an "Are you Sure" prompt as an alternative to this RFE. But it would need to be external. Something like:

    CHGCMDATR CMD(RSTOBJ) PARM(RSTLIB) OPTION(*DFT *INTERACT *CONFIRM)
    OPTION is a 3 or 4-part setting.
    1) The value of the parameter that evokes the action (3rd parm).
    2) The environment or MODE where run where this condition applies
    3) The action to perform. With *CONFIRM built-in but also a user-specified program to call would be nice.

    Then if I run RSTOBJ interactively and don't specify RSTLIB parm, it'll prompt me to confirm it.
    If I run RSTOBJ in batch, it will ignore this conditional action.

    Let me know if you think this is feasible and if I need to create a new RFE.

  • Guest
    Feb 16, 2022

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Languages - CL (Control Language)
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Core OS
    Operating system - IBM i
    Source - None