Skip to Main Content
IBM Power Ideas Portal


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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.

Status Not under consideration
Workspace IBM i
Created by Guest
Created on Apr 6, 2011

Add procedure documentation to content assist

The documentation of a procedure should be displayed right next to the list of possible entries offered by content assist (ctrl+space) for the current code.


Use Case:

Procedure documentation may look like this:

/**
* \brief Create JSON Object
*
* Creates a JSON Object.
*
* <br><br>
*
* The memory allocated for this object must be deallocated with the
* <em>dispose</em> procedure when finished.
*
* \author Mihael Schmidt
* \date 20.03.2008
*
* \return Pointer to the JSON object
*/
P json_create B export
D PI *
*
D jsonPtr S *
D header DS likeds(tmpl_header) based(jsonPtr)
/free


Example from the RPG Next Gen Editor which already does this:

https://sourceforge.net/dbimage.php?id=267540


Idea priority Medium
  • Guest
    Reply
    |
    Sep 14, 2015

    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

  • Guest
    Reply
    |
    Oct 9, 2012

    This RFE is a duplicate of another RFE. See for current status.
    Would it be sufficient to just show comment information in the content assist?

  • Guest
    Reply
    |
    Oct 13, 2011

    Thank you for taking the time to suggest this enhancement to our product. Many of our product enhancements result from feedback from our customers, so your input is always very important to us. We do not have plans to address your request over the next 18 months due to limited time and many competing priorities, but may consider it at a later time.
    If after 18 months, this continues to be important for you business needs, please feel free to resubmit for reconsideration during an appropriate planning cycle.
    Again, thank you for your suggestion and continued support!

  • Guest
    Reply
    |
    Jul 14, 2011

    Since both the "\" and the "@" are acceptable tag prefix characters it must be able to support both. Possibly make it a configurable option or parse both all of the time.

  • Guest
    Reply
    |
    Jul 9, 2011

    This RFE is consistent with our strategy and product roadmap and will be under consideration for a future release. Status has been updated to Uncommitted Candidate.

  • Guest
    Reply
    |
    Jun 1, 2011

    The display of the procedure documentation should support the rendering of HTML or any other well-defined external documentation syntax such as ILEDocs. This could be easily done by checking line 1 of the procedure header comments for a valid render type identifier (render.html, or render.iledocs, etc) and then supporting this with the ability to attach a renderer to the render type identifier in the LPEX Editor options.

    This way we can develop other documentation styles, or take adavantage of existing styles. A ILEDocs renderer within the LPEX Editor would be a great aid for developers.

  • Guest
    Reply
    |
    May 25, 2011

    I want to second the M_F and KurtAnderson comments.

  • Guest
    Reply
    |
    May 20, 2011

    This RFE is consistent with our strategy and product roadmap and IBM is continuing to evaluate.

  • Guest
    Reply
    |
    May 4, 2011

    As an extension of this request: a D spec keyword (Help('text')) at PR definition or parameters definition. So the help text will be available not only in content assist but also to PCL interfaces or other functions (EGL service generations, doc services etc...).

  • Guest
    Reply
    |
    Apr 14, 2011

    As an extension of this request, I would think showing the parameter names in content assist would be valuable as well.