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 245

iIn Debug Tool -Provide the reason for stopping at a breakpoint in the source view

User has requested that the reason for stopping at a break point in Debug Tool be provided in the source window when it sops at a line of code. Suggestion was to provide popup or message that was not in the log.
about 12 years ago in Debug for z/OS 3 Not under consideration

iIn Debug Tool -Provide the reason for stopping at a breakpoint in the source view

User has requested we provide the reason for stopping at a breakpoint on the source line when it stops. There is not log in the GUI interface to display the reason. He has suggested a popup at the line of source that the breakpoint stopped
about 12 years ago in Debug for z/OS 3 Not under consideration

CICS Debug start based on MQMD/DATA contents

Start debug on a CICS application where the transaction/application is started by CICS based on the content of an MQ message (non terminal transaction). The functionality would be very similar to what we have already where we can start debug of a ...
about 12 years ago in Debug for z/OS 2 Not under consideration

DT should better support a global preference (GBLPREF)-File with RDz

When you use full-screen interface a GBLPREF-file is usual and helpful to provide the users customized setup for DT, e.g. setting keys similar like a competing debugger to easily switch. This way a parallel used RDZ / Eclipse debugging will have a...
about 12 years ago in Debug for z/OS 3 Not under consideration

DebugTool should debug programs in CICSKEY and OPENAPI with TRANISO.

Debugtool loops with 'EQA9999W requested data set unavailable, looping 'if a CICS-COBOL program defined as OPENAPI and CICSKEY is being debugged in a CICS with TRANISO=YES. It turned out that COBOL Side file utility routine for CICS, IGZISFU issue...
about 12 years ago in Debug for z/OS 2 Not under consideration

Add support to display AR Registers

CITI has requested support to display AR Registers. It was verified with support that this is not available at this time
over 12 years ago in Debug for z/OS 2 Not under consideration

Allow for breakpoints prior to transaction

Need to be able to set conditional breaks before kicking off transaction.
over 12 years ago in Debug for z/OS 2 Not under consideration

Allow for breakpoints prior to transaction

Need to be able to set conditional breaks before kicking off transaction.
over 12 years ago in Debug for z/OS 2 Future consideration

security limitations in debug tool

I want to check the permissions of the user, the screen fields in DTCN or CADP, for example, limiting the user to debug only a specific program name or prefix, limiting to a specific user that started the transaction, a particular terminal, and so...
over 12 years ago in Debug for z/OS 3 Not under consideration

FIND command sets field protection on

FINDing in the LOG is generating a bunch of characters with NO-INPUT-attributes followed by funny colours (-> 03_after_enter.PNG) into the command line in log, can't overtype any of the line that contains highlighted piece (and get a usable cop...
over 12 years ago in Debug for z/OS 2 Not under consideration