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
Using the alias names for externally-described files or data structures makes the RPG code more readable. But it's difficult and error-prone to change an existing program to use the alias names instead of the short names, even using RDI's existing rename-refactoring feature. Currently, each field or subfield must be renamed separately, ignoring the errors from the refactoring about how the name comes from an external file.
It would be great if there was a refactor feature "Add Alias". That way, all the references to the related fields and subfields could be changed all at once.
I start with this code:
dcl-f orderfile;
dcl-ds orderDs likerec(orderRec);
dcl-ds otherDs likerec(orderRec);
dcl-ds custDs extname('CUSTFILE') end-ds;
...
custId = nextId();
if splrNm = *blanks;
...
orderDs.splrNm = getSupplier(orderDs.partNo : custId);
otherDs.partNo = 0;
I want to add the ALIAS keyword to the file and the EXTNAME data structure to get the source looking like this:
dcl-f orderfile alias;
dcl-ds orderDs likerec(orderRec);
dcl-ds otherDs likerec(orderRec);
dcl-ds custDs extname('CUSTFILE') alias end-ds;
...
customerId = nextId();
i f supplierName = *blanks;
...
orderDs.supplierName = getSupplier(orderDs.partNumber : customerId);
otherDs.partNumber = 0;
To use RDi's existing rename-refactor feature, I first have to rename each external field name and the subfield names in each LIKEREC data structure, and the subfield names in the EXTNAME data structure, ignoring the errors about breaking the link with the external file. Then I can add the ALIAS keyword to the file and EXTNAME data structure.
I would like to do this with one alias-refactor for the file and one alias-refactor for the EXTNAME data structure. The refactor for the file would add the ALIAS keyword and do a "rename" for both the standalone fields associated with the file and the subfields of the LIKEREC data structures associated with the file. The refactor for the data structure would add the ALIAS keyword and do a "rename" for the subfields of the data structure.
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 Power Systems Development - RDi team
The CAAC has reviewed this requirement and recommends that IBM view this as a high priority requirement that is important to be addressed. New and young developers to IBM i need to see that there is a path to easy and understandable code by first converting it/refactoring it. This preserves the argument that RPG is the language of business -- the first step in addressing older code is to convert it.
Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.
For more information about CAAC, see www.common.org/caac
Nancy Uthke-Schmucki - CAAC Program Manager
As we try to convince young programmers that it is easy to write in RPG because it is similar to other languages we can't keep presenting barriers like the traditional short name without a convenient solution. They have got to see that there is a path to easy and understandable code by first converting it/refactoring it. For me this is a high priority that preserves the argument that RPG is the language of business, and the first step in addressing older code is to convert it. This is an essential request to address as soon as possible.
We have reviewed this requirement and we feel it would be a beneficial enhancement to the product. We hope to be able to add it to our development plans in the future.
The COMMON Europe Advisory Council (CEAC) has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed.
Background: The CEAC members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.
To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT
Therese Eaton – CEAC Program Manager, IBM
Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.