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:

Status Not under consideration
Workspace Spectrum LSF
Created by Guest
Created on Dec 12, 2018

To be able to kill a specific process from a job


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 killing the whole job ?

Thanks you and best regards

  • Guest
    May 19, 2019

    lsrun is the only existing internal communication channel that could be used for this.
    If you disable lsrun, then an alternative would be to use ssh with the lsf-pam module to selectively allow a user to login to a node where they had work running to kill the process.

    Implementing an additional communication channel to kill a specific process could not be done as a patch.

  • Guest
    Feb 27, 2019

    To reply IBM_Systems_Developer:

    Many administrators choose to disable lsrun to avoid users from running high load jobs, bypassing LSF queues.

  • Guest
    Jan 4, 2019

    Is there any reason why the user cannot either ssh to the node and kill the process, or use lsrun?
    $lsrun -m gnbsx50588 kill 21851

  • Guest
    Jan 3, 2019

    That's a sweet requirement. It's what I call a gold nugget. I could see something along the lines of a PS line for the job too. That line would be captured at the running of bjobs and would provide all the processes in the control group, you could then use a command like:

    bpkill jobid [-m hostname] pid1 ...

    Very nice requirement indeed! Thanks!!!