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


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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

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.

IBM Employees should enter Ideas at https://ideas.ibm.com


ADD A NEW IDEA

Spectrum LSF

Showing 471

To be able to kill a specific process from a job

Hello, Sometimes, a job is completely stucked due to a specific process. Customer doesn't want to kill the whole job because he is waiting for the result of job. Would it possible to add the ability to kill a specific process from a job without ki...
over 5 years ago in Spectrum LSF 4 Not under consideration

Need lsmake which is supprts Gmake v4.2.1 or later

Current lsmake4 version supports GNU Make 4.0Customer environment uses Gmake v4.2.1 . We need lsmake4 to support Gmake v4.2.1 to enable make through LSF.
over 3 years ago in Spectrum LSF / Other 0 Planned for future release

Add quick help to RTM graphs when hovering the mouse on top of the graph

Show short help for each RTM graph while user hovers the mouse on top of the graph. Short help should have information of purpose of the graph and units of X and Y axels.
over 3 years ago in Spectrum LSF / Operations/RTM 1 Not under consideration

LSF doesn't allow multiple LOAN policies on the same hosts

LSF has limitation in SLA LOAN_POLICIES configuration by having only one loan duration time available. It would be great, if SLA LOAN_POLICIES can support option to LOAN for different time to different queues. For example:LOAN_POLICIES = QUEUES[ge...
over 3 years ago in Spectrum LSF / Administration 1 Not under consideration

LSF should always reject submitting jobs which request slots over slot limit.

A job with over limit slot request still can be submitted when the slot limit is configured with USERS. For example: With SUERS configured, job can be submitted and stays pending: Begin Limit NAME = TestQueueSiJobLimit QUEUES = priority SLOTS = 3 ...
over 5 years ago in Spectrum LSF 1 Not under consideration

RTM to/from LSF communication of Psusp-requeue job notifcation

We have reproduced the issue and it's a timing issue with RTM because LSF does not provide exitinfo when job's pre-exec fails and requeued. Since RTM relies on exitinfo to put it in the correct table, the changes will have to come from LSF. This w...
over 3 years ago in Spectrum LSF / Operations/RTM 0 Not under consideration

Preemption support for MIG GPU jobs

We would like that preemption will be supported also for MIG jobs(A100 dgx mig devices). Currently the preemption is not working for this type of jobs. Example scenatiois: kill two or more jobs and reconfigure mig to have the new job run. We need ...
almost 2 years ago in Spectrum LSF / Scheduling 2 Future consideration

Allow bjobs command to show the pre and post exec exitStatus/exitCode information

Right now, we require bhist to get any detail on pre/post exec error codes, it would be nice if we could get this from the job record via bjobs vs. bhist. bhist in very large environments is a non-starter for obtaining this status information.
almost 2 years ago in Spectrum LSF / Administration 1 Not under consideration

Allow Users to specify a ClearCase 'cleartool' command but require that it be white listed first

Allow the users to override the CLEARTOOL binary path, but only if it's included in a white list configuration file in the $LSF_ENVDIR location. I would suggest something like: cat lsf.daemons.wrap.conf /usr/altira/bin/cleartool /some/authorized/...
almost 2 years ago in Spectrum LSF / Administration 1 Not under consideration

Set more job variables in parent SBATCHD prior to forking the job SBATCHD/RES

I've been working with the Daemons Wrap source code trying to make the logging more presentable, and I've come accross a hurdle to effectively enhancing that integration. I need both the Job Start and Submit Times, and normally, I would just be ab...
almost 2 years ago in Spectrum LSF / Administration 1 Not under consideration