IBM Power Ideas Portal
Hide about this 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 (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 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 (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.

Add a new idea Subscribe
Status Future consideration
Workspace IBM i
Categories Languages - RPG
Created by Guest
Created on Nov 25, 2024

RELATED IDEAS

Add WHEN-IS-NOT clause to the new SELECT statement

See this idea on ideas.ibm.com

The traditional SELECT/ENDSL allows when a=b and also allows when a <> b. However, the new SELECT/WHEN-IS/ENDSL does not allow a negative comparison, and forces me to go back to the older style.

In this shop [and others I have worked in], this is used quite often in parameter passing to procedures where sometimes the parameter is checked via a SELECT against the value *LOVAL. Passing *LOVAL does special processing in the subprocedure.

Having WHEN-IS and WHEN-IS-NOT would allow the new SELECT clauses to be used in these procedures instead of reverting back to the old style.

I realize I can use WHEN-IS and OTHER, however, the bulk of the time the OTHER clause will apply and the SELECT will always check the WHEN-IS first, which 99 out of 100% is false. Allowing WHEN-IS and WHEN-IS-NOT allows the 99% comparison to happen first, the the 1% comparison to happen in that one case without checking the WHE-IS *LOVAL 99 time and failing.

Thank you.

Idea priority Medium
  • Guest
    Reply
    |     Mar 2, 2025

    Interesting idea. I suppose:
    SELECT code;

      WHEN-IS 3: // do something

    OTHER;  // effectively WHEN-NOT-IS  3:

    endsl;

    Possible, but I get what the requester is asking for. More capability than is currently offered in most other languages. I would be interested in previewing this design once you move forward with it.

  • Guest
    Reply
    |     Feb 12, 2025

    Also the following WHEN opcodes would be good:

    • WHEN-NOT-IN %LIST(...) | %RANGE(...)
    • WHEN-GT|LT|GE|LE <value>
       
  • Guest
    Reply
    |     Dec 23, 2024
    IBM will use this Idea as input to planning, but no commitment is made or implied. This Idea will be updated in the future if IBM implements it. IBM will use votes and comments from others in the community to help prioritize this Idea.

    If this Idea is implemented, it would most likely add support for the N extender for WHEN-IN and WHEN-IS to indicate that the condition is negated.

    SELECT X;
    WHEN-IS(N) *hival;
    // Handle the case where X is not equal to *HIVAL;
    WHEN-IN(N) myArray;
    // Handle the case where X is not equal to one of the elements of myArray
    ENDSL;

    -IBM Power Systems Development

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.