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 Delivered
Workspace IBM i
Created by Guest
Created on Feb 28, 2013

O-specs don't appear in the outline

In the Outline view list of field names used, it appears that O-spec references don't appear to be included in the list of data field line #'s being cross-referenced. Example: DC0175 uses field AMNAM1 that's coming in via a call to program MDAGC02. In DC0175, it's used 4 places (as a parm coming back from the call to MDAGC02, and 3 O-spec lines. The field list in the Outline view shows no ref's to field AMNAM1. I did find the one calculation section ref in the Outline view when I go to prototypes and click on the parameters for MDAGC02. AMNAM1 field is defined via a /COPY statement in the D-specs to source member *LIBL/QCPYSRC member: MDAGC02WF. Another example is workfield LIM1 is defined in the D-specs and is used in 4 calculation statements and 2 O-spec statements but all I see in the Outline view are the d-spec and 4 calculation cross-references.


Use Case:

O-spec references would appear to be included in the list of data field line #'s being cross-referenced, and increase developer productivity.


Idea priority Medium
  • Guest
    Reply
    |
    Sep 9, 2016

    This feature is now available in the IBM Rational Developer for i V9.5 product with V9.5.1 update installed.

    Product web page: http://www.ibm.com/software/products/us/en/dev-ibm-i
    Fix list: http://www.ibm.com/support/docview.wss?uid=swg27038481#9510
    Download doc: http://www.ibm.com/support/docview.wss?uid=swg24042646

  • Guest
    Reply
    |
    Jul 11, 2016

    The feature that is described in this request is a candidate for a future release.

  • 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
    |
    Jan 12, 2015

    At our shop, O-specs are primarily how reports are done. Even if we switched to using external print files (to which there is resistance), we'd have a lot of existing programs with O-specs in them.

  • Guest
    Reply
    |
    Jun 3, 2013

    This RFE will be under consideration for a future release. Status has been updated to Uncommitted Candidate.

  • Guest
    Reply
    |
    Mar 28, 2013

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