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.

Add a new idea Subscribe
Status Future consideration
Workspace IBM i
Categories RDi (Rational Developer for i)
Created by Guest
Created on Jul 10, 2018

RELATED IDEAS

Rdi Debug Step Over enhancement - Exec SQL statements

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 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.

Note - This may apply to other languages too

Note - replacement of RFE 121503: https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=121503


Use Case:

See Description


Idea priority Low
  • Guest
    Reply
    |     Oct 21, 2020

    We have reviewed this requirement and we feel it would be a beneficial enhancement to the product. We hope to be able to add it to our development plans in the future.

  • Guest
    Reply
    |     May 26, 2020

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. This function is available in green screen, so it should also be available in RDi. There is a work-around -- just put a breakpoint after the EXEC SQL statement, just as you can with EXSR, but this is a real annoyance to the developers to need to do this.

    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
    |     Mar 17, 2020

    The CEAC has reviewed this requirement and recommends that IBM view it as a HIGH priority requirement that is important to address.

    CEAC believes this nice to have has a high value to the broader community. The way the debugger works today is counter-intuitive for the user. It assumes you have a lot of knowledge of debugging and how the SQL precompiler works. How it behaves, it can be interpreted as an error, but it is not due to the invisible code that the precompiler generates.

    Background: The COMMON Europe Advisory Council (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
    |     Jun 11, 2019

    Mark Murphy - I asked that in my original RFE: https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=121503
    Which was declined, saying it was not feasible to step over an EXSR.

  • Guest
    Reply
    |     Apr 24, 2019

    It would be nice if step over also stepped over a subroutine rather than entering it. And Step to the end should step to the end of a subroutine.

  • Guest
    Reply
    |     Oct 19, 2018

    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
    |     Oct 2, 2018

    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 - Application Development
    Operating system - IBM i
    Source - None

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.