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.
We are adding support for PL/I macros incrementally. The first step is to avoid seeing syntax errors, which we are achieving with our new PL/I preprocessor support added with v4.5.0: https://ibm.github.io/zopeneditor-about/Docs/advanced_preprocessor.html. This will allow developers to run the compiler remotely for expanding the macros and see the results in Z Open Editor. We will be publishing a blog for how to do that shortly. Full editing support for code completion and preprocessor-free editing will be a future enhancement.
Example of code causing issues in the IDE:
SETMSG above is obviously not a valid PL/1 statement, so it is not recognized by the ide parser.
But SETMSG being defined as a macro procedure, and being active, replacement will occur during macro preprocessing and valid PL/1 code will be generated instead.
SETMSG should thus be accepted and ignored by the parser.