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 12, 2023

Debugger clean-up job should stop all debugger message regions that are waiting for input

We are using Debug for Z/OS in our test regions. We have scheduled the clean-up job to run every night. This job executes the Program EQANIPSB. It has 2 steps - the first step stops all the debugger message regions and the next step deregisters all the debugger transactions that users have registered to debug. The job works as expected most of the times. 

But when a debugger message region is waiting for input, the job does not stop the region. The stuck regions have to be manually brought down next day. This usually happens once or twice every week. If the clean-up job could handle stuck regions and bring them down, this would prevent us from having to bring them down manually.

Idea priority Medium