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 Oct 18, 2017

Change the name of "libevent.so".

We have "libevent.so" for our application.

LSF "libevent.so" conflict with it and we have to set library path for ours in job scripts.

"libevent.so" is too common name, so please change it in LSF, like "liblsfevent.so".

  • Guest
    Reply
    |
    Apr 6, 2018

    This one seems logical. I suggest we do this with any other *.so's that we use. We would continue to have 'some' of the old names as a legacy. For example, we currently have:

    Old Name New Name Keep OLD
    libbat.so liblsfbat.so Y
    liblsf.so liblsf.so N/A
    libevent.so liblsfevent.so N
    libglb.so liblsfglb.so N
    liblic.so liblsflic.so N
    libeas.so liblsfeas.so N
    libexp.so liblsfexp.so N
    libvem.so libegovem.so N

    We should also be versioning out so files to follow LSB. This way we can be more compatible with programs running using older versions of libraries.

  • Guest
    Reply
    |
    Oct 18, 2017

    Let me add some more information:
    1, This customer has to use LSF Session Scheduler feature.
    2, To work correctly, LSF Session Scheduler feature needs libevent.so which is provided by LSF.
    3, Technically, sbatchd adds $LSF_LIB:$LSF_LIB/ssched in the beginning of $LD_LIBRARY_PATH before starting ssched, in this way, ssched can start but customer's program (which uses their own libevent.so - in other place - will fail.).