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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace IBM i
Categories Languages - RPG
Created by Guest
Created on Oct 27, 2020

Prevent some RNF7031s. Add a way to indicate specific items which should not be diagnosed as un-referenced

Fields defined in ILE RPG source may be diagnosed as not being used by the program; but the developer may have reasons for keeping them. (They might be part of included files, part of API's, or intended for future use.)

It is suggested that a compiler directive or some form of source markup be created which the compiler will recognize and avoid issuing the RNF7031 (Name or indicator is not referenced) info message about specific fields or groups of fields as being not used in the program.

Furthermore, Rational Developer for i should then also recognize such markup when editing RPGLE source and not show the “is not used” annotations in the left editor margin.

Use Case:

As a developer editing RPGLE source in RDI, I do not want my editor view to be cluttered with certain "not used" annotations which I must ignore and can't or won't clean up.

Idea priority Low
  • Guest
    Mar 11, 2021

    IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it. IBM will use votes and comments from others in the community to help prioritize this request.

  • Guest
    Nov 25, 2020

    IBM has received the requirement and is evaluating it. IBM will provide a response after evaluation is complete.

  • Guest
    Oct 31, 2020

    Practical issues of implementation aside - RDi already provides a simple mechanism to avoid having to see such messages. Simply change the error list setting to not include info messages. The only time I ever see such messages is the time between doing a new instal with a clean workspace and changing the setting after my first compile.

    It would also clutter up the source horribly which would make it harder to read.

  • Guest
    Oct 30, 2020

    You could create a dummy subroutine or procedure referencing the field you don't want to see.
    The dummy subroutine / procedure is not called anywhere in the program.

    then put a statement like

    eval theFieldIDontWantToSeeUnreferenced = theFieldIDontWantToSeeUnreferenced;

    in the dummy subroutine / procedure.