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.

Add a new idea Subscribe
Status Future consideration
Workspace Debug for z/OS
Created by Guest
Created on May 30, 2025

RELATED IDEAS

RDS (EQARMTD) and zOpenDebug are not currently sysplex-aware, so they can't redirect our debug request, and we cannot always pick up IMS transactions for debug.

We have an issue using the z/OS Debugger in VS Code, due to our setup in Test where we have two LPAR’s in a Sysplex.
Since our IMS transactions are automatically placed on either LPAR, we need to be able to pick up the transaction from either LPAR at any one time.
The issue is that we can only have one zOpenDebug host at a time, making it extremely tedious to debug at the moment.

We would like to avoid defining two launch configurations in launch.json, if possible. If we click "Debug", we would like to catch the transaction in a debug session, ALWAYS.

Developers are NOT able from the client applications to direct the transactions to one specific LPAR.

We have also been playing with the idea of stopping the IMS transaction in one "leg", so that the transaction is forced to execute in one specific LPAR, but that seems like an inferior solution.

Is this solvable?

Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.