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
Created by Guest
Created on Dec 16, 2019

Debugging in RDi should require only one step over EXEC SQL statements

It would ease debugging if we could compile programs with compile option DBGVIEW(*NOSQLSRC) No SQL source.
This would skip over all embedded sql statements but still would allow them to run.


Use Case:

This saves time when you are debugging programs and don't want to spend time debugging over the embedded sql statements.


Idea priority Medium
  • Guest
    Reply
    |
    Sep 25, 2020

    This RFE is a duplicate of another RFE. See https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=122252 for current status.

  • Guest
    Reply
    |
    May 12, 2020

    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
    |
    Apr 29, 2020

    Here is a sample program with an EXEC SQL statement. Using the system debugger (STRDBG), it only requires one step to step over the EXEC SQL statement when using the source view. Using the RDi debugger, it requires several steps because there are actually several program statements involved in the EXEC SQL statement, which you can see if you debug from the listing view.

    dcl-s x char(10) export;
    exec sql set :x = 'hello';
    return;

    Compile the program with CRTSQLRPGI DBGVIEW(*SOURCE).

  • Guest
    Reply
    |
    Apr 29, 2020

    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
    Component - RPG/COBOL Development Tools
    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
    Reply
    |
    Apr 29, 2020

    IBM has modified some of the information in this request. Please contact us if you have any questions.

    Specifically, the Headline (Title) has been updated to clarify the scenario.

    Previous Headline: Add RPGLE Compile option to not debug embedded sql

    New Headline: Debugging in RDi should require only one step over EXEC SQL statements

  • Guest
    Reply
    |
    Apr 28, 2020

    When you debug using RDi, everytime you step over an exec sql statement, it takes multiple steps to finally get past it.

  • Guest
    Reply
    |
    Apr 16, 2020

    Normally, the system debugger only requires one step in the debugger to step over an EXEC SQL statement when using the default "SQL Root Source" view.

    Please provide an example of an SQL statement that requires more than one step when using the SQLRPGLE source view.

  • Guest
    Reply
    |
    Feb 17, 2020

    The COMMON Europe Advisory Council (CEAC) has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement (SCR instead of SQL) 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
    |
    Dec 17, 2019

    Hi Niels,
    Thanks for that, I do like your suggestion that the default changes to SRC instead of SQL.

    Marina

  • Guest
    Reply
    |
    Dec 17, 2019

    What you ask for actually exists. It is one of the available debug view: SRC, SQL and LST. Maybe this RFE has to change to the debug view by default will be SRC and not SQL.