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 Jul 10, 2013

Allow DT to "trap" on calls made to linked in C modules under CICS (in a long running C based task)

Consider the following scenario (we use RD/z with Debug Tool):<br /><br />CICS Region Startup (driven by CICS PLTPI initiation) <br />CFISTRT1 <br />    … <br />    … <br />    CICS LINK UMISTART <br />          CICS LINK UMQSCHED <br />                CICS START UMQSERVI (Long Running task) <br />    … <br />    … <br />End CFISTRT1 (Startup Code) <br /><br />… <br />…      Some time goes by <br />… <br /><br />UMQSERVI <br />    … <br />    … Some initialization code here <br />    … <br />    Do while (1)                                    Do Forever <br />          …           <br />… Some application logic here <br />          … <br />          … <br />          Status = UMQRESND (a, b, c);    <-----------------Trying to stop when this module is invoked <br />    … <br />    … <br />/*------------------------------------------------------------*/ <br />/* Build ecb list for waiting                                                                  */ <br />/* 3 conditions waited on                                                                          */ <br />/*      - Shutdown command, ecb in ccanchor                                            */ <br />/*      - Timer from a new msg, ecb in ccanchor                                    */ <br />/*      - Interval from the POST command below, calc by UMQCALCI */ <br />/*------------------------------------------------------------*/ <br />ecb_list[0] = &ccanchor_ptr->umqshutd;                          <br />ecb_list[1] = &ccanchor_ptr->umqtimer;                          <br />… <br />… <br />/*------*/                               <br />/* Wait */                               <br />/*------*/                               <br />ecb_list_ptr = &ecb_list;                <br /><br />EXEC CICS WAIT                           <br />        EXTERNAL                       <br />        ECBLIST      (ecb_list_ptr)       <br />        NUMEVENTS (UMQSERVI_EVENTS);   <br /><br />    End While <br />End of module UMQSERVI <br /><br />UMQSERVI is the Load Module <br />UMQRESND is an object module linked into UMQSERVI <br /><br />With the Call to UMQRESND, we cannot get DT to stop consistently when it enters UMQRESND.<br /><br />DT support tell me that it is in the C runtime that the problem lies in. In other words, the called module is not a C enclave.<br /><br />From DT Support:<br /><br />For long running tasks running C, DT only gets the chance to pattern match (and decide to start up) at enclave (or "CICS Program") start. <br />Since there is no enclave start in the DO FOREVER loop, nothing calls DT to do pattern matching, so DT does not start.

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 - Other

  • Guest
    Reply
    |
    May 11, 2020

    This has been implemented via delay debug

  • 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
    |
    Jul 23, 2013

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Enterprise Tooling
    Product - IBM Debug Tool
    Component - Other

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - C/C++ Compilers
    Component - Miscellaneous