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 option to specify jobs for which detailed thread data should be OMITTED from the QAPMJOBMI file
In a large system environment, where there are jobs that are known to generate millions of secondary threads per day, Collection Services becomes almost unusable due to the amount of data in the QAPMJOBMI file.
This request is to provide an option to specify a job name, where secondary thread data from that job is not populated into the QAPMJOBMI file.
The file already includes a count of the number of threads created and the number of active threads, so there is data in the file that can be used to understand threading characteristics without the detail data of every thread.
The Management Collection object can contain the full set of data; the request is simply to exclude the thread data from the file.
This support needs to be part of the configuration when creating the database files during each interval collection, as well as when doing a full create of the performance data from the management collection object.
The client has a single job that generates millions of secondary threads each day. Many of these are short-lived and the JBSLTCNT count is incremented.
However, there are a sufficient number of threads that live more than one second such that the QAPMJOBMI file is around 34GB for a 24 hour collection.
The current circumventions are to expand the short-lived thread lifetime beyond one second, and to cycle the collection every 4 hours.
While these circumventions are helpful, an option to completely omit this thread data from the QAPMJOBMI file for jobs that are known to create millions of secondary threads would make analysis of the performance data faster, as well as more useful.
Having the full set of data in the Management Collection Object would allow for the option to create the file data with all threads included if this is required for analysis.
Do not place IBM confidential, company confidential, or personal information into any field.