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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Some time back we tried activating Debug Manager in our SYSPLEX environment.
At the time, it did not work as we hoped, due to the missing sysplex awareness.
In short, any debug session which would use the Debug Manager service, would need to be running on the same lpar as the user was signed into zOS Explorer/Debug Manager.
This can not be guaranteed as lpar affinity, and CICS load balancing does not allow to direct/force a debug job to be on just one lpar in the plex.
In Debug Manager configuration instructions, I have noted that a reference to the loopback adapter is made.
https://www.ibm.com/docs/en/adfz/developer-for-zos/15.0.0?topic=considerations-loopback-localhost
That made me wonder: What if the lpar local debug manager STC, would try connecting to the RSE daemon via the external load-balancer interface to the sysplex.
That way, the debug manager will find the correct lpar for the signed in user, and it would then resolve the client IP address correctly?
In the current setup, where the interface must be found as localhost in the hosts. file, this is of-course not possible, but is there a STC only mechanism for supplying the "localhost" ip address, and that way ensure the Debug Manager functionality?
Thank you for taking the time to suggest an enhancement to our product. Many of our product enhancements result from feedback from our customers, so your input is always very important to us. We feel this is a valid requirement but delivery within the RFE two year window is not likely. We would recommend opening a similar RFE against IBM z/OS Explorer as sysplex awareness would need to be supported there before considering support in Debug Manager. Again, thank you for your suggestion and continued support.