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


Status Not under consideration
Workspace Spectrum LSF
Created by Guest
Created on Sep 4, 2018

bkill instrumentation/logging to find source

Currently the bkill command only tracks (lsb.events) who ran it, and what signal was sent. If we have a heavily active user with a broken script, it is very challenging to find the source of the bkill command.

It would be valuable to log the source host and maybe even process ID ($$) in the "JOB_SIGNAL" log entry

  • Guest
    Reply
    |
    Aug 21, 2020

    Using bkill -C would seem to be the best solution for this

    $ bkill -C "From host: `hostname`" 357
    Job <357> is being terminated
    $ bjobs -l 357
    ...
    Mon Feb 10 21:21:24: Completed ; TERM_OWNER: job killed by owner; Kill Re
    ason: From host: lsftest01.
    ...
    $ bhist -l 357
    ...
    Mon Feb 10 21:21:24: Signal requested by user or administrator
    ; Kill Reason: From host: lsftest01;