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
The content of the LPEX Outline view should be exportable. It would be a great basis for application documentation—even better if the context help for procedures/fields/constants would be included. JSON or XML would be fine maybe also a readable format like HTML.
I was not the first having this idea. There was an RFE about the same topic in 2016, but it had been declined because of the prospects to have RPG Docs supported in the future (originally the future of 2012).
Idea priority | Medium |
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.
Thanks for pointing out IleDocs. The Halcyon Visual Studio Code extension uses the IleDocs syntax to enhance the context help if I understand it correctly; that’s great, but still no export. IleDocs looks great, especially the examples I saw in its Sourceforge wiki. However, I’m quite sure I am not able to install the current version of IleDocs from Bitbucket in the near future, it’s all Greek to me.
PS: RDi team, what did you mean by "iDoc"—was it just short for IleDocs or is there an RDi feature, I missed so far?
So IleDocs is an expansion of RPGDocs that is gaining wider acceptance https://halcyon-tech.github.io/docs/#/pages/developing/iledocs
IBM Power Systems Development - RDi team
I apologize, I’m not familiar with iDoc, and a web search only resulted in an SAP tool with the same name, so I don’t understand your question.
The export should provide procedure names and information such as return value names and types, parameter names and types and the comments adjacent to the prototype definition (as the context help does); also file definitions (in the future hopefully including files, that are used in embedded sql). Work variables and constants need not be included—for my purposes.
PS: The only one who seems to have heard about "iDoc" is chatGPT—but they could not provide a single working link to an iDoc documentation or even a mention. But you are human, right? :-)
IBM Power Systems Development - RDi team