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
Provide error handler for secondary thread of multi-threaded job
When a multi-threaded job encounters an unhandled exception, the system should be able to gracefully handle the error with the standard *INQ message to *EXT or QSYSOPR.
Background When an unhandled exception occurs in the secondary thread of a multi-threaded job, instead of displaying the *INQ message panel for user response, the job loops on the error, filling the job message queue and crashes.
It is very important to have the error handling stability that IBM i has always had.
This is a poor way for IBM i to handle errors. The standard way has always been for the system to send *INQ~ to *EXT or QSYSOPR for handling by the user.
This problem came up when an SQL user-defined function had been incorrectly created without the "not fenced" statement to indicate "run single-threaded". When the job ran, SQL started a second thread. The function tried to use commands and programs that were not coded "thread safe", and the system tried to send *INQ to *EXT, which looped and crashed
Possible solutions 1. Allow the *INQ message program and display file to be used in a secondary thread. 2. Send the *INQ to QSYSOPR for handling.
Do not place IBM confidential, company confidential, or personal information into any field.