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.

Status Not under consideration
Workspace Debug for z/OS
Created by Guest
Created on Feb 24, 2012

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. In a recent customer experience, they could not user SCHDTYP=PARALLEL due to program limitations. When we implemented the exit, other transactions waited while the debugging a transaction. We learned that we need to set transaction classes up such that only the transaction being debugged would flow to a single MPR, while the other transactions would flow to another MPR. None of this is documented, nor nothing is done within the IBM Debug Tool to change the transaction classes during the debugging session. Recommend a thorough review of this environment, and Debug Tool improvements to minimize mass changes to IMS parameters, and improved documentation in this environment. See the attachments for details of this problem.

Idea priority High
  • 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
    |
    Oct 23, 2013

    This requirement is rejected based on the new IMS debugging features added to Debug Tool V13 that overrule this requirement.

  • Guest
    Reply
    |
    Mar 29, 2012

    See related RFE 20881 Improved Debugging for IMS Message Processing Programs

  • Guest
    Reply
    |
    Feb 24, 2012

    Attachment (Description): IMS Parameters that were recommended, but could not be used in the customer environment

  • Guest
    Reply
    |
    Feb 24, 2012

    Attachment (Description): Emails depicting the problem with debugging MPRs