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
Categories Db2 for i
Created by Guest
Created on Jun 4, 2018

Resolve object references for embedded SQL at compile time

Product: Change Management

Our change management application allows us to track changes, automate our deployment and development process, and perform impact analysis, all of which give us better controls and reduce risk in our software development lifecycle.

Description: Our team uses change management for impact analysis and object relations. Like many change management applications, the data available is returned from the compiler through functions such as DSPPGMREF. This should be extended to return object relations that are in embedded SQL when the object can be resolved at the *MODULE level.

Use Case:

System: Change management
Actor: Developer

Use cases for the system:
-Developer compiles *MODULE object type with embedded SQL
-DSPPGMREF executes

When using DSPPGMREF, tables and objects referenced in embedded SQL that can be resolved at compile time should be returned in the same way that file definitions would be.

Idea priority Medium
  • Guest
    Apr 17, 2021

    IBM does not intend to provide a solution to this request at this time, so it is being closed. SQL services are being developed as an alternate interface for CL commands and other IBM i information. IBM prefers to invest resources in an SQL service rather than in an enhancement to the DSPPGMREF CL command.

    An RFE to return DSPPGMREF as an SQL Service that is being considered. SQL module level information could be added to this service:

    Module level SQL references can be returned today with the following query:

    select program_schema, program_name, module_name, statement_text, p.*
    from qsys2.sysprogramstmtstat,
    table (qsys2.parse_statement(statement_text)) p
    where program_schema = 'MYLIB'
    and program_type = '*MODULE';

  • Guest
    Jan 21, 2020

    The CAAC has reviewed this requirement and recommends that IBM view this as a high priority requirement that is important to be addressed. Since DSPPGMREF includes *MODULE as an object type, we feel that this information should be available there for consistency.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see

    For more details about CAAC's role with RFEs, see

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Dec 3, 2018

    The fact that the bind is able to include the information in the SRVPGM makes me believe it is available in the MODULE object as well but somehow not shown. I hope IBM pays attention to this as it is major drawback for SQL and proper change management.

  • Guest
    Jul 5, 2018

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Db2 for i
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Languages - RPG
    Operating system - IBM i
    Source - None

  • Guest
    Jun 5, 2018

    We have the same problem. When we use a SQL in a *MODULE object and then do DSPPGMREF on the module, the file references DO NOT appear. However, if we subsequently bind the module in a service program, we do see the references when we do DSPPGMREF on the service program.

    Apart from the fix, any workarounds would be welcome.

    Example module source:

    ctl-opt nomain;

    // --------------------------------------------------
    // Procedure name: READ
    // Purpose: Read a record
    // Returns:
    // Parameter: SQL => SQL Instruction
    // --------------------------------------------------
    DCL-PROC ReadRecord EXPORT;
    DCL-PI *N;
    SQL CHAR(250);
    END-PI ;

    exec sql
    insert into omrel (elobjc)
    select 'A'
    from omobj
    where rjobjc = 'DDD';
    return ;
    END-PROC ;

    ### procedure prototype
    // --------------------------------------------------
    // Prototype for procedure: READ
    // --------------------------------------------------
    DCL-PR ReadRecord;
    SQL CHAR(250);
    END-PR ;


Provide file usage of modules on DSPPGMREF

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. U...
about 5 years ago in IBM i / Languages - RPG 4 Not under consideration