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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Threshold for over allocation in License Scheduler
Based on the license availability and the demand from certain project(s), LSF License scheduler can allocate more license to a project, then its define share of licenses. If limits are defined, it leads to under utilization and wastage of licenses...
The LSF License Scheduler now supports RLM as well as FlexLM, but LSF Explorer only supports FlexLM.An RLM dataloader is needed for Explorer to allow the RLM licences configured in License Scheduler to be monitored.
Availability of Max used License Scheduler managed license token in LSF job records
License Scheduler keeps updating LSF job records for the actual number of license tokens used by the job. At the end, only the last used value of the license token is kept in the job records. LSF should record the maximum number of token used by L...
License token distribution without share based calculation by LSF License Scheduler
In License Scheduler it is mandatory to configure Project mode or Cluster mode and specify the shares for all the defined Features.However, some license tokens are not tied to any project or cluster and should be distributed freely, without any fa...
Transfering free value to another project in LS immediately
< Condition >Let's suppose,- There are two prjects in LS, prj1 and prj2.- There are two license features, lic1 and lic2.- There are two free lic1 and many free lic2 are remained.- Between prj1 and prj2, SHARE mode, 50%:50%.So, for lic1, prj1...
We are troubled by the slow dispatch time of jobs, when the license scheduler is involved. Even after lengthy optimization, the dispatch time remains at 10-25 seconds, which is not good. (note that LMSTAT time and interval is just 3 seconds).If th...
Have License Scheduler Automatically Prune its Database
LSF License Scheduler can create a database directory that log's token usage by feature. Over years, this directory can become cluttered, and impact License Scheduler performance. There should be a setting in License Scheduler to prune that dire...
Display Dynamic Priority (for project group nodes)
Ability to display dynamic priority in License scheduler for project group nodes. Currently if priority is not set on a particular level there is no way to display the preemption order, which makes it difficult to explain the decision-making proce...
Do not place IBM confidential, company confidential, or personal information into any field.