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.
In the above IBM Case we described a problem on one of our customer's system, whereby a PROC(00) data set was moved by the customer to a new volume and the catalogue entry adapted (DELETE & DEFINE NONVSAM). We do realise this is not a good thing to do. We have NODSI defined in the PPT.
Two weeks later one of the four systems in the JESplex suffered JCL errors from all submitted tasks, the other three were still running ok.
Idea priority | High |
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.
The $TPROCLIB command without any parameters resolves issues like that. But I agree that JES2 should be able to react on such a situation by itself and only issue a message when it can not clear the situation on its own.
And yes, a frequent check that alerts someone before jobs start failing, would be helpful.