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.
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.
IBM has received the requirement and is evaluating it. IBM will provide a response after evaluation is complete.
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.
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.