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
RDI LPEX Editor add Signature Feature to COBOL Source Members
In the LPEX editor for RPG, you have already implemented the 'signature' option so the user may specify a text string to be inserted into each line of a source member added/modified by the user.
Can you please implement this same feature for COBOL source members? Columns 1-6 are available for this purpose.
The RPG implementation is a global option, so the same text is applied to all open source members. If you could implement the feature exactly like RPG that would suffice at minimum, but as a further enhancement I would like to see the 'signature' option available for each open source member independently, not at the global editor level. See the use case for an example of how this would be helpful.
This feature is primarily used to identify the user making edits to a source member, and serves as additional information to supplement the date stamp already added by the editor. It is very useful when a program is maintained by a team.
If the signature were specific to each source member, it could be used to include release/version data to narrow the edits for future programmers.
For example, "DFv1.8" for source member A in one tab, but "DFv6.4" for another source member being edited in the same session.
Do not place IBM confidential, company confidential, or personal information into any field.