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
Created by Guest
Created on Jun 20, 2018

Rdi Debug of RPG Step Over enhancements - EXSR and Exec SQL

Currently when debugging RPG code with RDi, Step Over will step over procedure/function calls but will step into EXSR subroutine calls. It should also step over EXSR subroutine calls. Subroutines have similar use cases to subprocedures (and some shops stick with subroutines out of old habit), so there is just as much reason to want to step over a subroutine as a subprocedure.

Currently when debugging RPG code with RDi in *SOURCE view, Step Into and Step Over will have to be pressed an unknown number of times times to clear a single Exec SQL Statement. This is because the SQL Precompiler replaces Exec SQL Statements with multiple assignments and procedure calls that are invisible in *SOURCE view, but visible in *LIST view. Step Over on an Exec SQL statement in *SOURCE view should step over the invisible SQL code and skip to the first executable line after the Exec SQL Statement.

Use Case:

See Description

Idea priority Low
  • Guest
    Sep 18, 2018

    I'm wondering why IBM_Rational_Developer (I don't mean the person but the organisation) can not open the separate RFE regarding SQL.
    Why do we customers have to do such work?

  • Guest
    Jul 6, 2018

    We have evaluated this request and determined that it cannot be implemented at this time because it is not feasible to step over an EXSR operation.

    Regarding the extra stepping required to step over an EXEC SQL statement, please open a separate RFE against the system debugger. Specify Brand = Servers and Systems Software", Product Family = "Power Systems", Product = "IBM i", Component = "Application Development".

  • Guest
    Jun 26, 2018

    Michael - I only mentioned RPG because that's all I program in. If other languages would benefit from this, then by all means list them.

  • Guest
    Jun 25, 2018

    I would be very supportive of this, but it should apply to more than just RPG.

  • Guest
    Jun 21, 2018

    Same for the native debugger... especially the SQL remark is very annoying.