This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 updateson 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
Allow conditional service break point in iASP environment
Conditional service breakpoints do not work in an iASP environment. The 'WHEN' clause on a service breakpoint does not work in an iASP envrionment.
We have thousands of jobs and threads servicing tens of thousands of customer connections to our system for ordering our products. When a production issue is reported and we need to debug a specific customer job/thread, it is impossible to identify which of the thousands of jobs is receiving the specific request such that we can debug the program.
Before we went to an iASP machine, we could put a program into debug mode, then add a service breakpoint with a 'when' condition such that we only go into debug mode when that condition is met.
"SB 842 USER BOB WHEN CUSTOMERNO=12345"
This puts program PROGRAM1 into debug mode and only stops the one job/thread that meets the conditions of user 'BOB' calling the program with input parameter CUSTOMERNO=12345. Thus, even though we have thousands of threads calling the same program, we only halt the one job/thread associated to this specific condition, and all other connection requests then get routed to another available job/thread since our serviced job is now in debug mode and waiting for our input.
However, this 'WHEN' clause is not allowed in an iASP environment. So now, the best we can do is add a service breakpoint in a program on a specific line for a specific user. However, if the job happens to use a generic user like QUSER, and it's a high usage program, we now essentially halt all production threads calling program 'PROGRAM1' with user 'QUSER'...and the volume of customer requests/threads is so high we have no chance that we'll be halting the one specific job/thread we want.
This is a crippling limitation in our ability to debug and triage issues without bringing our entire system to a standstill. We need the 'WHEN' clause for service breakpoints to work in an iASP environment.
Do not place IBM confidential, company confidential, or personal information into any field.