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 Delivered
Workspace Debug for z/OS
Created by Guest
Created on Oct 7, 2014

Debugging in IMS with Debug Tool

1) It is common to have IMS transactions switching to others, so, we should have how to specify different transaction codes (I suggest 15), to better filtering. Filtering by CU names must be maintained, as long as the multiple tx. id filter.

2) Specifying CU names does not work well in IMS, since subprograms are dynamically called, CUs are only recognized if they are the main LE program. Called subprograms should be recognized too.

3) Debugging of transactions called by generic users is confusing and cumbersome:

1st., someone edits EQAZDSYS in SEQATLIB and fills the following parameters (there are other optional parameters too):

TUXRFDSN The data set name for the cross reference table.
TUGNRCID One or more generic IDs separated by a blank.

Afterwards, the developper creates an entry in the cross reference table:

Developer userid X tx code. Note that the from (generic) userid is not a part of the xref table entry.

Finally, the developer updates his/her EQAUOPTS data set.

Compare to CICS Debugging, where everything is informed in DTCN, including a different userid and matching strings in container/commarea

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
    |
    Jun 3, 2015

    Status update for this requirement:

    Item 1 has been addressed: We added a new panel to DTU option 6 to capture up to 15 transaction names

    Items 2 and 3 are currently being worked on which will result in significant usability improvements in the area of IMS transaction debugging.