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 Sep 5, 2017

RELATED IDEAS

Including program name and other information in the StartStop message information for Debug Tool for z/OS

As the developers adopt Debug Tool as their development tool for debugging applications and collecting code coverage information, it is important to have the accounting information about who is using the tool, as well as which programs they are working with. The request is to have this information as an account of use for Debug Tool. Our suggestion is to include program name, date-time of compilation (to identify which program copy is being used) in the StartStop messages, since they already have Userid, date-time for the beginning of the session, environment (batch, CICS, IMS) and date-time for the ending of the session. Also the XML format for this file (startstop messages file) is fine to extract easily the information. And finally, this information could be collected without interference of the developer, since the option for the startstop message (yes or no) and the name of the file where the messages are recorded, both are defined in EQAOPTS module. This feature needs to be available for all methods Debug Tool is started (TIM, batch, CICS, IMS, RDz), since the information collected refers to the use of the product. If possible, it would be interesting to have the information about which type of session the developer have done: debugging, code coverage, both.

Idea priority Medium
  • 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 6, 2017

    Just to clarify what we stated about the "type of session", it is very useful to have the type as a code meaning:
    1) a debugging session, a code coverage session or both
    2) for each one of them, the detail, as a TSO, batch, IMS, CICS, running under TIM, RDz, as an example.

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.