This is the public portal for all IBM Z Hardware and Operating System related offerings. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
LE to allow UNIX System Services to interrupt an LE program utilizing Pause/Release.
System: LE on z/OS USS
Actor: SAP support experts or any other USS C code developer with the necessity to debug the stack trace of a process
SAP support experts want to use dbx -a <processId> to get program stack traces on single and multi-threaded processes like the SAP Enqueue Server (enserver), for example to analyse performance issues.
This is currently -ONLY- possible with Business interruption. Either the process has to be stopped and restarted to use a specific environment variable, if the support expert happens to know, or if not, even worse, the process gets killed by attaching dbx. This is not acceptable for our large banking clients for example. The Enqueue Server is a core component of SAP. Crashing as well as stopping and restart results in a Business outage and clean-up operations.
For SAP Enqueue Server you have to define the environment variable _CEE_CONDWAIT_PAUSE=NO in an SAP profile and to restart it in order to be able to switch sucessfully to all threads of this process. Otherwise the dbx fails with ptrace return codes: ret=-1, errno=143, errno_jr=0x0d3d017f and Enqueue Server crashes too. In this case SAP support experts cannot easily interpret why the dbx fails.
So if a SAP support expert advices the customer to run dbx on this SAP process as on any other platform, it will crash, meaning an unplanned outage of SAP for some time and cleanup activities. This is not acceptable for a business critical application like SAP on Z. Clients run SAP on Z actually to avoid such unplanned outages.
This behaviour of dbx is obviously caused by changes made with LE APAR OA55202 (PTF UA96854 for z/os 2.3). Before this APAR and on z/OS release 2.2 and prior dbx -a worked fine for multithread processes.
Allowing UNIX System Services to interrupt an LE program utilizing Pause/Release might help dbx to deal with multithreaded processes.
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.
.Hi Volker, the only thing LE can do is to avoid using Pause/Release by default, that is change default value of _CEE_CONDWAIT_PAUSE to NO.
That has the same effect with specifying _CEE_CONDWAIT_PAUSE=NO explicitly in application.
Our concern is there could be performance degradation, I think this is also your concern.
The real solution has to be covered by z/OS USS kernel component. They has another RFE open, see below link:
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=144810
Hi, is there any progress? regards, Volker.
This item is not in our plans but is being kept in our backlog.