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
With fixpack 8.5.1, RDP Content Assist no longer picks up mixed case subfield names on data structures defined like a file.
For example, if I have a file with a single field called CUSTNUM, if I use content assist on a data structure defined like that file, the subfield would appear as CUSTNUM. However, once I typed it into the RPG source as CustNum, Content Assist used to display the subfield as I had typed it. Now it's not changing and is only displaying the all-upper-case subfield.
Being an picky programmer, I don't code anything in all upper case except constants. Having the auto-completion use the upper case only reduces the functionality of Content Assist because I will no longer use the auto-completion function on data structure subfields (which has been very handy).
In the screenshot I supplied, the data structure that is being used in the Like statement is a Template defined using LikeRec. I underlined a subfield that I feel should have appeared in mixed case instead of all uppercase.
I was using this functionality every day, many times a day. We use a lot of qualified data structures and the auto-completion has been amazing. I feel like this has been a big step backward.
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Programming Languages
Product - Developer for Power Systems
For recording keeping, the previous attributes were:
Brand - Rational
Product family - Design & development
Product - Developer for Power Systems
This feature is now available in the IBM Rational Developer for i V9.0 product.
Product web page: http://www-03.ibm.com/software/products/us/en/dev-ibm-i
Fix List: http://www.ibm.com/support/docview.wss?uid=swg27038481
Download doc: http://www.ibm.com/support/docview.wss?uid=swg24034857
This request is approved and planned for delivery within the next year or next generally available release. Thank you for taking the time to suggest this enhancement to our product and for your votes.
This RFE will be under consideration for a future release. Status has been updated to Uncommitted Candidate.
This RFE is consistent with our strategy and product roadmap and IBM is continuing to evaluate.
Attachment (Description): Example 2 of the subfield appearing in uppercase when it should/was appearing in mixed case.
Attachment (Description): Example 1 of the subfield appearing in uppercase when it should/was appearing in mixed case.