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 Client Install
Created by Guest
Created on May 21, 2010

Modify RDz to allow breakpoints to be set outside of a debug session.

Recently, while attempting to resolve a tech support issue (PMR 62618,756) it was discovered that breakpoints cannot be set in code unless the code is already stopped at an execution point (i.e. - The compiled source code is already executing under 'Debug As' with the execution point stopped at the first line of code. Most debuggers that I have used (gdb, Visual Studio, Microfocus NetExpress, Eclipse (with Java, PHP, etc.), etc.) all support the placement of breakpoints before code has started execution, and I feel that RDz should have the same capabilities. Currently, breakpoints that are created in RDz are preserved between debug executions, so there must be some context for maintaining breakpoint information outside of the executing debugger, so it should be technically feasible to permit the setting/updating of breakpoints outside of the executing debugger as well. Even if breakpoints can only be set/modified in the Debug Perspective (without the debugger running), it would be a considerable improvement in usability).

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 - Developer for System z

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

  • Guest
    Reply
    |
    May 3, 2013

    Since the original RFE is dated spring 2009 I wold like to have it reconsidered, as we have same problem, using PLI.

  • Guest
    Reply
    |
    Jun 14, 2010

    The direction for RDz debugging is to support breakpoints in the program source. This includes adding the breakpoints in the source before the program has been started.
    The level of support for this feature is program language specific. This means that some languages will be able to support this feature sooner than others.
    For example C/C++ on System z uses the program source for debugging and therefore will be able to support this feature much sooner. COBOL and PLI debug from the compiler listing and will require additional compiler support to debug from the source before this feature can be fully implemented. The request is currently not in plan to be delivered within the next 2 years.