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 Db2 for i
Created by Guest
Created on Jul 19, 2018

Allow use of RPG procedures in embedded SQL as host "variable"

When writing embedded SQL, host variables should be real variables instead of expressions which requires additional step to define extra work variables and assign the expression in advance to the work variable.


Use Case:

An example might be as follows;

Exec SQL update mytable set field = :MyRPGFunc(x);

instead of

Dcl-S workField VarChar(128);
workField = :MyRPGFunc(x);
Exec SQL update mytable set field = :workField;


Idea priority Medium
  • Guest
    Reply
    |
    Nov 4, 2020

    IBM does not intend to provide a solution to this request at this time, so it is being closed.

    This would be a costly enhancement to implement. Embedding RPG language constructs within SQL would require the SQL precompiler to recognize and handle a new type of replacement variable. Today, the ILE RPG precompiler has limited awareness of RPG procedures.

    Additionally, before we could consider implementing this enhancement, the IBM SQL Language Council would need to agree that allowing host language syntax to be used in an SQL statement is an appropriate extension of the SQL language. Since the interface between SQL and host languages is intended to be limited, approval is not guaranteed. The new SQL syntax would need to be appropriate for multiple embedded languages as well.

    For these reasons, IBM has decided not to invest in this enhancement.

    As an alternative, we recommend defining scalar functions and using those functions in the SQL statement.
    For example, the RPG code could look something like this:

    CTL-OPT Nomain;
    DCL-PR RPGFUNC1 VARCHAR(128);
    P1 VARCHAR(128);
    END-PR;

    DCL-PROC RPGFUNC1 EXPORT;
    DCL-PI *N VARCHAR(128);
    P1 VARCHAR(128);
    END-PI;
    dcl-s nbr VARCHAR(128);
    nbr = P1;
    return nbr;
    END-PROC;

    The function definition would look like this:

    CREATE OR REPLACE FUNCTION QGPL.RFUNC1(
    P1 VARCHAR(128)
    )
    RETURNS VARCHAR(128)
    LANGUAGE RPGLE
    PARAMETER STYLE GENERAL
    EXTERNAL NAME 'QGPL/TEST(RPGFUNC1)';

    The example update statement would look like this:

    Exec SQL update mytable set field = qgpl.rfunc1(:x);

  • Guest
    Reply
    |
    Mar 17, 2020

    The CAAC has reviewed this requirement and recommends that IBM view this as a high priority requirement that is important to be addressed. This will provide benefit to an overwhelming majority of application developers.

    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 www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Reply
    |
    Feb 18, 2019

    The COMMON Europe Advisory Council (CEAC) has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed.

    Background: The CEAC members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial 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.

    To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT

    Therese Eaton – CEAC Program Manager, IBM

  • Guest
    Reply
    |
    Jul 27, 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 - Client

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Developer for Power Systems
    Component - RPG/COBOL Development Tools
    Operating system - IBM i
    Source - Client