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 JCL the TIME parameter is used to limit the CPU time of jobs. Originally used to limit CPU times to save costs and find looping jobs. Through the introduction of Java this parameter will "misbehave" or leads to misunderstanding. Those jobs will be shutdown long before actual GP time limit is reached. Because Java runs on TCB in zIIP so therefore those times are also considered in the calculation for JCL TIME. That means if someone is using Java this limitation of CPU time through JCL TIME must be set with a new value... Means remeasuring. Very unproductive because that must be done for every job.
It would be better to have a JCL parameter that really reflects only CPU time spent on GP. Customers could leave the value that is already set untouched and only need to replace the parameter itself.
In JES2 these TCB on zIIP times are also considered (IEF032I output).
It would be great to
Implement a JCL parameter that really only takes GP time into account
Not adding the values of Java TCB like the JCL TIME parameter
Enhance documentation of JCL TIME by adding the hint or information that also Java TCB times are also added to this value.
That would prevent misunderstanding and the requirement to explain this specific behavior when using Java.
Thank you very much.
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.