Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Workspace Spectrum LSF
Components Administration
Created by Guest
Created on Apr 10, 2020

job group management improvement

checking log file of RTM server, we found a recurrent warning triggered by too many job group for one of our LSF cluster. this highlight that we cannot have more than ~7000 job group for a cluster, the impacted cluster having ~30k explicit job groups.

In this cluster, we found plenty of job groups that what not used since years.
checking more deeper, we found that many job groups have very big number of records in the file: for ex, some of them have more than 100000 GRP_ADD/CTRL records. For a 1.8 Million records file, we found 1.2 M GRP_* records for less than a 1000 active job groups !

Can you please provide some extra features to manage job groups:
a parameter to define an explicit job group TTL ?
a new option to the bgdel command to clean up all job groups not used since a duration ?
change the behavior of the to not multiply GRP_ * records for the same job group.