Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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
Categories EGL Language
Created by Guest
Created on Dec 19, 2012

show executing code in debug

System: Product RBD 8.5
Actor: Program Developers

Description: during debugging of EGL porgrams in the RBD Debug perspective, one cannot know what the program is doing in between map converses. It could be in DB2 CICS or program logic and the programmers has no way of knowing. It would be very helpfull to have a line execution view that would show each source code line as it tis being run.

Idea priority High
  • Guest
    Reply
    |
    Sep 14, 2015

    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 - Business Developer

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Business Developer

  • Guest
    Reply
    |
    May 12, 2014

    Thank you for this suggestion. We we do not expect to implement it because we have not received the information needed for more than 6 months.

  • Guest
    Reply
    |
    May 12, 2014

    Thank you for this suggestion. However, we do not expect to implement it because we have not received the information needed for more than 6 months. Please provide the additional information and reopen it if you still need this functionality.

  • Guest
    Reply
    |
    Jan 25, 2013

    This has been reviewed by development. We think you want the editor to update to the current file and line being executed by the debugger, without having to use step. We believe that the debugger would not perform well when running with this type of feature enabled. It would be hard to see most of what is taking place, since things are executed so quickly and the editor would constantly be flashing.
    We'd like to offer a counter proposal, which will provide the same type of information you request without having much of an affect on performance. We will provide a new view called "EGL Debug Trace" which has a checkbox to enable tracing. When this view is open and the option to enable tracing is turned on, the debugger will print each statement as it's being run. This provides information about what's being done without the user having to manually step through the code. If the user wishes to halt execution so that variables can be inspected, there is already a "suspend" button in the Debug view that does this. The value displayed for a statement will not be the original line of code from the source file, but will instead be a string representation of the IR. If you click on a statement from this view and it has corresponding source available, we will open the source file and highlight the line for the statement. This view provides a recording of what was run so you can look back at the execution flow. The view will have the option to limit the number of lines of output, just like in the Console view. Changes to the tracing enablement will take immediate effect, and the debug session will not need to be restarted (this lets you narrow the scope of what gets traced). The EGL interpretive debugger will support this new view but the EGL Rich UI debugger will not.
    Please let us know if you are OK with our proposal.