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
When debugging an exception error that can cause the debugged program to end is sometime encountered. However if no breakpoint is established at that stmt, the program just ends. This is most notable in RPG IV and compiled SQL/PL. Add a "Pause on Exception" as we see in most other debug agents on other platforms, that stops when an exception/error is detected that isn't trapped by user-code.
I kind of feel like this used to be a thing... I have a breakpoint on statement 1000 and an error occurs a few line above or below, the problem terminates and I never see what happened in debug. There should be an option to stop/pause/break on exceptions in the system debugger. Perhaps a parm on STRDBG.
Do not place IBM confidential, company confidential, or personal information into any field.