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 Not under consideration
Workspace IBM i
Created by Guest
Created on Oct 23, 2015

"Open Declaration" should actually open the declaration

When doing a "Open Declaration" on an externally defined procedure or field, RDi simply jumps to the line in the existing source where the procedure or field is imported. This is the easy way out and is not very helpful.

Use Case:

In the case of copy books, the IDE knows which copy book contains the declaration, and all the capabilties to open copy book and jump to the declaration are already part of RDi. Instead of showing the line where the copy book is imported, the IDE should open the copy book and jump to the the ACTUAL declaration.

The same could be done for fields declared in external files. Most user created objects on the system have the source code location as part of their service-related attributes. The command RTVOBJD is able to obtain the source location from the object (when available). It seems to me that RDi should be taking advantage of this. If the object definition contains a valid source location, it seems like the IDE should be smart enough to open a READ ONLY version of that source and jump to the line where the field is ACTUALLY declared. The IDE already retrieves the the fields that are defined in the various external files. It seems that grabbing the source code location for the object during that processing should be possible.

One issue is that SQL tables, views, and indexes will not have a source location defined in their service-level attributes. If an object's source is not found, but the SQL source is retreivable, you COULD give the user the option to retrieve the SQL. I would consider that an optional feature, but it is certainly a feasible work around for objects created using DDL.

Idea priority Medium
  • Guest
    Nov 2, 2017

    This RFE is a duplicate of another RFE. See 23923 for current status.

  • Guest
    Jan 27, 2016

    This is very similar to RFE 23923 from 2012, except for the external objects part (which seems like overkill to me).

  • Guest
    Nov 5, 2015

    For the copy book use case:
    Although the theme is consistent with our business strategy, it is not committed to the release that is currently under development.

    For the other use cases, we have evaluated and determined that they cannot be implemented at this time because they are not consistent with the rest of our product.