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).
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.
Then it seems my suggestion #2 could come into play - send an *INQ to QSYSOPR as is done with batch jobs. This would prevent the wildly crashing job syndrom in the event of an error.
You can send Inquiry messages from a secondary thread. But you cannot get input from the user (the reply) because there is no workstation support for multiple threads. Sending the default reply in this situation is the correct action to take.
There are no plans to support workstation I/O from secondary threads. Allowing WS I/O from a secondary thread would potentially create deadlock situations between the primary and secondary threads that cannot be prevented by the OS.
Creating the SQL user-defined function to run single-threaded is the correct action to take.
Creating a new RFE based on Community RFE #88223 in product IBM i.