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.
S222 abends are generally expected when the RESTFiles requests have finished their processing. When a request first arrives, REST Files creates a TSO Address Space to handle the request, which remains available after use so that subsequent requests can process in that same TSO Address Space. However, it can only service one request at a time. If another request arrives while z/OSMF is still processing a request, a second TSO address space will be created (and so on). Once the work is done and there are no longer any requests, the z/OSMF tasks are terminated, which would result in the S222 ABENDS that are seen. It can lead to massive S222 and corresponding S013E Logrec entries if running automated as it opens one IZUFPROC per request. It also issues
BPXP018I THREAD 1932F80000000000, IN PROCESS 83951862, ENDED WITHOUT BEING UNDUBBED WITH COMPLETION CODE 40222000, AND REASON CODE 00000000.
per requested IZUFPROC.
z/OSMF does not provide a timing parameter or something similar to prevent S222 abends and to finish IZUFPROC orderly.
Nightly, in our environment we create hundreds of API RESTFiles calls automated which creates a heavy overload of these Abends and Message Flooding and corresponding number of useless S013E SW Logrec errors.
Idea priority | Medium |
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.