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 Jun 14, 2018

Do not mark data structure or other container as unreferenced when any subfield is referenced

In recent releases of RDi, unreferenced variables and file declarations are marked with an information annotation.

If a data structure is not, in itself, referenced, it is so marked.

But any subfield that IS referenced is not marked.

I want the containing data structure NOT to be so marked when any of its subfields is referenced.

Here is an example of a PSDS, where the actual data structure will rarely be referencedas a whole but the JOBNBR subfield would definitely be referenced.

dcl-ds pgmStatDS psds;
jobNbr char(6) pos(264);
end-ds;

As for a file declaration, it might be marked as unreferenced even when the record format IS referenced.

Here is an example that involves a file, an I/O data structure, and the use of that data structure when writing to the record format:

dcl-f rphHrsSkp usage(*output);
dcl-ds outHrsSkp extname('RPHHRSSKP' : *output) qualified inz end-ds;

eval-corr outHrsSkp = lRphHrs;
write rlRphHrsSk outHrsSkp;

The dcl-f is marked as unreferenced, but when I comment it out, the write statement fails with a couple "not defined" messages (RNF7503 & RNF7030).


Use Case:

These annotations that indicate when a "container" is itself not referenced are confusing and can lead to unnecessary work, if a developer removes the "unreferenced" item and compiles, just to find that the compile fails.


Idea priority High
  • Guest
    Reply
    |
    May 28, 2019

    This feature has been delivered as part of the Rational Developer for i V9.6.0.4 product.

    Fix list and link to download doc: https://www-01.ibm.com/support/docview.wss?uid=swg27038481#9604

  • Guest
    Reply
    |
    Jul 9, 2018

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

  • Guest
    Reply
    |
    Jul 5, 2018

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Reply
    |
    Jul 2, 2018

    I have experienced another situation.

    Given the same data structures described below:

    In the code you have
    eval tmpTheDS.field2 = 123456
    but field2 in theDS is marked as unreferenced.

    If I want to clean up my source and delete the line with field2
    then I have a compile error because it now no longer exists in
    the tmpTheDS data structure.

  • Guest
    Reply
    |
    Jun 15, 2018

    I have experienced that if you have a situation like this:

    theDS is a qualified data structure with fields field1, field2 and field3
    tmpTheDS is a data structure defined using likeds( theDS )

    in the program tmpTheDS is referenced
    eval tmpTheDS = theDS
    eval tmpTheDS.field2 = 123456

    then tmpTheDS is marked as not referenced for some reason.

    ( I'm using RDI 9.6.0.3 )