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

All ideas

Showing 6102

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

Provide a tracking facility for the Debug Tool Terminal Interface Manager.
almost 13 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...
almost 13 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
almost 13 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.
almost 13 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.
almost 13 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...
almost 13 years ago in Debug for z/OS 3 Not under consideration

Remember file name in the Terminal Interface Manager panel * Specify TEST Run-time Option Data Set *

Customer has complained when using PF10 on the Terminal Interface Manager, the panel * Specify TEST Run-time Option Data Set * does not remember the data set name used for EQAUOPTS. For this customer we customized the EQAD3CXT module to use a pref...
almost 13 years ago in Debug for z/OS 2 Not under consideration

DESCRIBE ALLOCATIONS

Is there a way to limit the result of the DESCRIBE ALLOCATIONS command to the STEP ou JOB for a batch applications ? The problem occurs only when starting the debug session using DTU option 2 and using the TSO session as 3270 interface for the deb...
almost 13 years ago in Debug for z/OS 2 Not under consideration

Improve debugging in an MPR environment with the EQAD3CXT exit

There are many challenges with using the EQAD3CXT exit in an IMS MPR. There are many IMS parameters that must be set correctly in order for the transaction to begin debugging. These parameters are NOT documented in the IBM Debug Tool publications....
almost 13 years ago in Debug for z/OS 6 Not under consideration

Improve Debug Tool Interrupt Capabilities

Interrupt Capabilities: Debug Tool needs the capability to stop after x number of calls to Debug Tool, and ask the user if they want to continue. Some languages offer the abiltiy to stop using the Attention key. However, this does not always work....
almost 13 years ago in Debug for z/OS 5 Not under consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.