This portal is to open public enhancement requests against IBM Z Software products. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
IFTHENELSE is very useful in converting C code to PL/I (and in writing some new PL/I code), but we're not so sure that adding the complexity of these additional functions to the language is worth the cost (to language complexity amongst other things)
i don't think introducing such a new construct will improve code (in any way).
:-)
SELECTWHEN would be useful to prevent having to write nested IFTHENELSE which could rapidly become unreadable
What is wrong by putting a normal SELECT statement before the call of MyProc? I decidedly vote "NO" for this.
What is wrong by putting a normal SELECT statement before the call of MyProc? I decidedly vote "NO" for this.