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 the addition of **FREE support for RPGLE, the prior use of columns 1 - 5 goes away. However, the vast majority of developers use these 5 characters to put a 'change mark' to tie source code changes back to a project or reason for the change. Tying changes back to projects and often regulatory mandate for change is often done in the insurance industry (and I am sure other industries as well). The 'change mark' is not a functional part of the source code, but rather a meta-data "key" to an often much larger, external set of data. It does not lend itself well to placing at variable positioning inside a source code line.
It would be greatly beneficial to add a 5 character 'change mark' field to source files on the IBM i. This new, metadata element would go hand-in-hand with RPGLE developers embracing the **FREE format. As a metadata element, it makes the source code more intelligent. Losing this tie back to enterprise level project data discourages RPGLE developers from moving existing source code forward to **FREE. Suggestions that RPGLE developers move forward without this meta-data element are quite literally missing-the-mark. Suggestions that RPGLE developers all move to IFS and GIT without the Source Change Date, Line Number, and Change Mark is to ignore the "Advanced System" element of the systems design.
Source code editors could make the additional field available to developers so they do not lose the source code change management value that columns 1 thru 5 provided prior to fully **FREE format RPGLE.
The field could be named SRCMRK, since developers refer to the value in positions 1 - 5 of RPGLE as the 'change mark'.
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.
It is not possible to add another column to source physical files.
-IBM Power Systems Development
The CAAC has reviewed this IBM Idea and recommends that IBM not implement this request.
This is not consistent with IBM direction for good programing practices. Outside of Source management tools, current practices are to use comments.
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 IBM Ideas on the broader IBM i community and has therefore reviewed your Idea.
For more information about CAAC, see www.common.org/caac
Carmelita Ruvalcaba - CAAC Program Manager