This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
In the 'License Scheduler' product, monitor only necessary features instead of all
sometimes, we encounter slowness (freezes) on LSF jobs scheduling due to big slowness in licenses monitoring (lmstat) from License Scheduler because license features used for some resources under LS management are part of license services managing thousands of features for 10 thousands end-users.
When license service works fine, it takes ~30s to get data for all features and less than 5s for the concerned features.
When there's issue to monitor license service, it takes more than 10mns to monitor all features but only ~30s for the desired features.
Can you please improve the license monitoring by doing lmstat per feature instead of all ?
If the behavior (global vs per feature) could be selectable using a switch, it would be a plus.
As a side effect, it will also reduce the load on the license server (KBs of data instead of MBs for several thousands of token).
Do not place IBM confidential, company confidential, or personal information into any field.