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).
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.
See this idea on ideas.ibm.com
Please remove restrictions in RDI when editing code for a RPG program. The problem occurs for the F-Spec continuation line that RDi rejects. The specification works normally in SEU.
The F-Spec and I-SPec are used to rename a record format and fields from a table definition that has a underscore in the name and the format name is longer than 10 characters.
There are many clients using older RPG code which they do not want to upgrade to ILE. (Another issue).
As we move forward, we are using tables with long names but these pose a problem for RPG 3/4 programs where we need to rename the record format and field names.
In RDi, it rejects the statements. I found that SEU works as designed and could get passed the problem that way, but it wasted a good few hours trying to resolve the issue not expecting RDi to be the problem.
Here is the example code:
Idea priority | High |
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.
IBM has identified this as a defect with the OPM RPG syntax checker requiring a code change. Please contact your service representative to open a Case and mention this RFE. Note that there is a preference to turn off the OPM RPG syntax checker, found at
Preferences > Remote Systems > Remote Systems LPEX Editor > IBMi Parsers > RPG/400 where you can uncheck "Automatic syntax checking".
I agree that this is either a bug or a configuration issue and not likely to be missing functionality
Can you please include the continued F-Spec that is giving trouble
Are you sure that the file is found in the library list (otherwise we will warn you that we did not find the external definition being referred to).
Surely this is a bug - not an enhancement? RDi should support it. Period.
Attachment (Use case): Example of error messages in RDi.