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 Future consideration
Workspace Debug for z/OS
Created by Guest
Created on May 20, 2022

Delay debug does not behave like CICS debug

Hi,


we found some weird difference in behaviour of z/OS Debugger between CICS and non-CICS profiles (delay debug).

Assuming we have a program call chain of PROGA calling PROGB and defining both programs in the debugger profiles.


Behaviour in CICS: Debugger stops at every occurence of all programs when developer issues 'Resume' in between.

Bahaviour in batch: Debugger stops at the first program in the list of programs which starts. After issueing 'Resume' the job runs to finish, even if other programs in the profile run in this sequence.


As a developer I would assume both behave the same. Also it would ease debugging multiple programs in batch. By now I have to start debugging first and then add one or more entry breakpoints.

Idea priority Medium