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 Delivered
Created by Guest
Created on Jul 16, 2010

RDZ Debug. Manage compiled language event breakpoints

Consider this code:

call xx();

xx: proc;
dcl i fixed bin(31);
do i = 1 to 100;
put skip data(i);
end;
end xx;

If you run this in the debugger and on the call xx(); statement you press "step over", you will never the less enter the xx procedure, and the cursor will position it self om the "put skip" line having i=60;

This is because an ENDPAGE event is fired after 60 new lines.

In the breakpoints view, when debug session has started, you can press "manage compiled language event breakpoints" and here the default is set to TEST(ALL).
If you change this to TEST(ERROR) or TEST(NONE) , then ENDPAGE is not caught.

We need a preference that allows us to set TEST(ERROR) as the default.

In the above example the consequence is not that big, but if the call is to an external module that has not been compiled with debug info it begins to get messy.

Idea priority Medium
  • 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
    |
    Sep 14, 2010

    It's true that TEST(ERROR) is saved for the next debug session when changed by the user.

    In our shop we offer (or rather force) the users to start up whith a pre-configured workspace containing all the settings needed.
    So I would like to now where in the workspace this information is stored. If it is possible to change a xml file or some preference file that will do the trick - but I can figure out where in the workspace this information is stored.

  • Guest
    Reply
    |
    Aug 24, 2010

    In RDz the changes made on the "Manage compiled language event..." dialog are global and saved. The changes made to that dialog will be used in the next zOS debug session. So you should only need to set the TEST(ERROR) once and all future debug sessions will use that value. As far as this request is concerned it should work as you requested as long as you are using RDz v7.x and above.

    One thing to note....If you change workspaces it will default back to TEST(ALL) since the profiles are stored in the workspace. If you are NOT seeing the above behaviour then please let us know and we can investigate.