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 Not under consideration
Workspace IBM i
Categories Languages - RPG
Created by Guest
Created on Nov 29, 2018
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit IBMI-I-1715 Resolve object references for embedded SQL at compile time.

Provide file usage of modules on DSPPGMREF Merged

When a module uses embedded SQL, the file usage is not shown on DSPPGMREF OBJTYPE(*MODULE) unlike it is for normal programs or even service programs.

The problem is that this limits impact analysis as most tools operate on DSPPGMREF information.


Use Case:

When a module uses embedded SQL, the file usage is not shown on DSPPGMREF OBJTYPE(*MODULE) unlike it is for normal programs or even service programs.


Idea priority Urgent
  • Guest
    Reply
    |
    Dec 3, 2018

    I haven't exactly checked how it is done for a SRVPGM or PGM but having the same behavior would already be fine. Since the information becomes visible once modules are binded together in a service program, the information must already be present somewhere.

    But since this is a duplicate it is best to discuss this in the original RFE.

  • Guest
    Reply
    |
    Nov 30, 2018

    Your request is a duplicate of RFE 120837. Please use that RFE to cast a vote or add a comment.

    http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=120837

  • Guest
    Reply
    |
    Nov 30, 2018

    It is a great idea - and I will vote for it ;

    The solution could be quite simple for static bound cursors, updates and delete where the statement have a direct description of resources i.e. in "select * from customer" where customer is a table.

    However - How would you implement it if the usages was a view and/or a dynamic sql and/or stored procedure and/or UDTF?

    My point is : The levels can be rather deep and the dependencies are sometimes solved by context. so a DSPPGMREF will sometimes not show the complete truth.

  • Guest
    Reply
    |
    Nov 30, 2018

    It is a great idea - and I will vote for it ;

    The solution could be quite simple for static bound cursors, updates and delete where the statement have a direct description of resources i.e. in "select * from customer" where customer is a table.

    However - How would you implement it if the usages was a view and/or a dynamic sql and/or stored procedure and/or UDTF?

    My point is : The levels can be rather deep and the dependencies are sometimes solved by context. so a DSPPGMREF will sometimes not show the complete truth.