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 244

Add message for wrong command

If you type a wrong command, such as typing A in the prefix area for a commented line, there is no message in the header. You must always keep the log open and check the results of every operation...Do not forget to check that the SET LOG command ...
over 12 years ago in Debug for z/OS 4 Not under consideration

Allow for Logical Unit names other than EQAMVnnn

Allow customers more flexibility, possibly via a USERMOD, in naming the Logical Units (LU's) used by Debug Tool.
over 12 years ago in Debug for z/OS 3 Not under consideration

Provide ability to read TIM ACB from a parmlib member

With multiple versions of EQAOPTS with different TIMACB LU names we need a unique EQAOPTS per sysplex. This is not a clean instal with SMP/E, and causes problems with CICS reading one version of the EQAOPTS (in the TLIB) and the programs reading a...
over 12 years ago in Debug for z/OS 2 Not under consideration

Multiline instructions in COBOL

LangX and Sysdebug have different support for automonitor and list prefix command.Sysdebug works as described but LangX monitor line per line and does not support the L prefix command.
over 12 years ago in Debug for z/OS 2 Not under consideration

Track usage if the Debug Tool Terminal Interface Manager (DT TIM)

Provide a tracking facility for the Debug Tool Terminal Interface Manager.
over 12 years ago in Debug for z/OS 3 Not under consideration

Retain Condition Codes with the IBM Debug Tool Batch JCL Utility

The Batch JCL Utility strips off condition codes from the JCL when processing a JCL member. This results in jobs failing, where they would normally be successful. For example, some jobs test for the existance of a file, and if it does not exist, a...
over 12 years ago in Debug for z/OS 2 Not under consideration

add timestamp in location

Add the timestamp of the csect in the location to confirm we are debugging the correct version of the load
over 12 years ago in Debug for z/OS 4 Not under consideration

Incomplete location

program ::> csectThe location in the header displays only the csect, not the program.
over 12 years ago in Debug for z/OS 4 Not under consideration

Increase the Limitation of 1000 inter LU's for DT

Currently DT is limited to 1000 internal LUs. Customer has stated they feel they will have up to 2000 or more users at the same time. This is the EQAMVnnn LUs.
over 12 years ago in Debug for z/OS 3 Not under consideration

Improve how JCL procedures are located with the Debug Tool Batch JCL Utility

Improve how JCL procedures are located with the Debug Tool Batch JCL UtilityDTSU and the IBM Debug Tool Batch JCL Utility do not resolve the location of procedure libraries the same as JCL/JES does. Consider the following scenario: A job is submit...
over 12 years ago in Debug for z/OS 3 Not under consideration