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.

ADD A NEW IDEA

Debug for z/OS

Showing 246

Externalize the PSBNAME for debugging sessions

Parker Hannifin has requested we add the PSBNAME of the program that is being debugged. This would be very helpful information since the program can be referenced by multiple PSBs. This is especially helpful when debugging IMS MPR programs.
over 7 years ago in Debug for z/OS 2 Not under consideration

Improve trap condition on Debug for z/OS

Improve trap condition of task we want to debug by adding MQDATA field.Be able to use this field to specify data to check in MQDATA to begin debug session.
almost 4 years ago in Debug for z/OS 1 Not under consideration

Debug Tool - add support for protected assembler debugging

Current the Debug Tool does not support debugging of protected assembler modules making it impossible to debug some of our system exits and applications. I'd rather not have to switch to a product that supports this functionality since our user ba...
almost 8 years ago in Debug for z/OS 2 Not under consideration

Change Debug Tool to allow the remote debugger (RDz) to allow valid Cobol command to MOVE SPACES to GROUP-ITEM

The Enterprise Cobol compiler (v4.2) allows setting the value of a group item as a standard COBOL statement, but RDz/Debug Tool does not allow it. It begins with a Working Storage definition like this: 01 WS-VARIABLE. 05 WS-ITEM1 PIC 9. 05 WS-ITEM...
over 11 years ago in Debug for z/OS 4 Not under consideration

DEBUG Load Module Analyzer include Compiler Version (5.1, 5.2) in output

Update the Load Module Analyzer report to include the compiler version. The report currenty provides Enterprise COBOL for z/OS Version 5. Is it possible to differentiate 5.1 from 5.2 and 6.1 from 6.2?
almost 8 years ago in Debug for z/OS 2 Not under consideration

Allow to reload the debug file manually

Manually reload debug file that was created under USS.1) When the auto debug file load fails, the source code view has 1 blank line only. I cannot reload manually.2) When the debug file path in the load module is not available in the test z/OS USS...
almost 4 years ago in Debug for z/OS 2 Is a defect

Show previous line of code when the AT CHANGE or watch breakpoint is encountered

When a watch breakpoint or AT CHANGE breakpoint is triggered, the debugger depicts the next statement in a program. Customers have asked to show the previous statement in this scenario. Statements may not be contiguous. For example, consider a wat...
about 4 years ago in Debug for z/OS 1 Not under consideration

Include execution times for Code Coverage reports

In the Code Coverage result we can see the percentage of execution coverage for each routine, and we request to show the time spent to execute the routines.
over 8 years ago in Debug for z/OS 2 Not under consideration

PD Tools Code Coverage Plug - Name in the Code Coverage Report is not persistent

When you double click on the Code Coverage Report Generation line in the Debug Tool Code Coverage pane, you are presented a Code Coverage Report pane where you enter the name of the code coverage output data set. This name is not persistent. So, w...
over 8 years ago in Debug for z/OS 3 Not under consideration

Sys Prog

There are no exclusion parms in LMA - so I have been asked to open a this RFE and request selection options.
over 4 years ago in Debug for z/OS 4 Not under consideration