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 Subscribe
Status Not under consideration
Workspace Debug for z/OS
Created by Guest
Created on Feb 21, 2014

RELATED IDEAS

Usability improvments to Debug Tool

Improve usability. Make the product appear more "customer friendly" rather than allowing the underlying technology or product to respond in ways that confuse the customer. There are several requested improvements.
a) If a CEEOPTS TEST parameter is present, issue an error for invalid syntax, or if the debug session can not be initiated. Customers view the lack of error as a product defect. In comparison, the EQAD3CXT exit, tracing levels can be set to depict if something is not initiated. Nothing like that is available for the CEEOPTS statement.
b) Eliminate confusing messages in the Debug Tool log, specifically the SVC Screening message, the INSPPREF message.
c) Eliminate the IEC141I 013-18 messages when a save settings member is not found. Eliminate the similar message when SET DEF LIST points to several libraries, and the module is not found.
d) Automatically set the defaults so that users do not have to use SET TEST ERROR, or the installer to set THREADTERMCOND to NOPROMPT only for CICS Environments. I install a global preference file with commands to "fix" this issue.
e) When in a CICS Environment, set the default exit to QUIT DEBUG TASK or QUIT DEBUG, which ever command works best to eliminate the 4036 abends when getting out of CICS.
f) Eliminate the need to SET WARN OFF for COBOL 3.4 when using GOTO, JUMPTO, or changing storage.

Idea priority High
  • Guest
    Reply
    |     May 19, 2021

    As part of the review process, we strive to be transparent about our intentions with each RFE. The offering team has carefully reviewed this RFE and has decided that it does not fit into our current plans within the next 1-2 years, so the RFE will be closed. The request will be kept in RFE system and might be reassessed or reopened for additional feedback or voting in the future. We value your feedback and thank you for allowing us the privilege of partnering with you in developing our products.

  • Guest
    Reply
    |     Apr 15, 2021

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Development Tooling
    Product - IBM Debug for z/OS
    Component - z/OS Debugger

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Development Tooling
    Product - IBM Debug Tool
    Component - Host

  • Guest
    Reply
    |     Nov 19, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Development Tooling
    Product - IBM Debug Tool

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Tooling
    Product - IBM Debug Tool

  • Guest
    Reply
    |     Apr 8, 2014

    Please add QUIT DEBUG when debugging IMS MPRs also. Here is the issue when one issues a QUIT or QQ.

    Terminating IMS programs when testing with Debug Tool
    James Rice on 08/05/2011 at 12:48 PM
    Category: IBM Debug Tool


    (From Doug Stout)

    Some IMS environments (IMS/TM, BMPs when IRLM/DBRC are active and logging) are a little different from other non-IMS environments in that IMS has problems when a program does not return control to IMS when it is done.

    The bottom line is that a user should not use a QUIT or QQ command in Debug Tool in these environments. QUIT DEBUG or QUIT ABEND are OK. I've seen some IMS users change their default PF3 key to QUIT DEBUG so they don't hit it by mistake.

    In IMS, the call chain goes: DFSxxxxx (one of the IMS controllers) -> AppProg. IMS requires AppProg to return control back to DFSxxxxx when it is done. The only permitted exception is when the application abends, and the IMS controller still gets control back during abend processing. A QUIT or QQ command terminates AppProg (like a STOP RUN in COBOL) and the DFSxxxxx program never gets control back, and it never gets a chance to terminate the thread, release locks, etc. So from IMS's point of view, the program is hung up.

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.