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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Prevent unknown RPGLE language features from breaking validation/outline view
Working for a financial company, users are extremely limited in their ability to download and install updated versions of developer tools. It can be years between updates to Rational Developer, as getting a new version requires a lengthy verification, packaging, and deployment process.
That means we usually do not have support in RDi for the more recent language features.
That in itself isn't too bad as the RPGLE code will still compile and run just fine. The issue is that often using an unknown language feature (e.g. a Built-in Function unknown to the RPGLE inline code validator) will cause RDi to stop parsing the source from that point on. This can not only break inline code validation from that point on, marking every source line from then on read as invalid, but can also cause Outline view to be completely blank.
It would be nice if RDi could recover more gracefully from "seemingly-invalid" RPGLE code so even though the unknown language feature may show a validation failure, the rest of the source does not.
This would help encourage devs to try new language features where otherwise they may not - and in my experience devs simply sticking with what they know instead of exploring new features is a big problem among many IBMi shops, so anything that can be done to help with that is good
Do not place IBM confidential, company confidential, or personal information into any field.