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 497

Keep in memory jobs killed over PTL (Pending Time Limit)

Hi, following suggestion in IBM support case. We see that jobs killed over PTL are immediately removed from LSF master memory so that even while a job ID was issued during submit, status check via bjobs/bhist does not find such job ID resulting in...
3 months ago in Spectrum LSF / Operations/RTM 0 Delivered

Need PAC version supported by rhel 9.4 and higher.

We plan to roll out rhel9.4 and rhel9.5 onto our cluster in the coming days. So, we need the PAC version to be supported. Kindly help us in providing the respective PAC version which supports rhel 9.4 and higher.Right now latest version of PAC 10....
5 months ago in Spectrum LSF / Installation 1 Delivered

lsf.conf documentation should report which daemon(s) need restart

Every time an lsf.conf entry is recommended by Support, I have to turn around and ask which daemon (or daemons) need a restart, which causes delay. The developers already know what daemons are affected by the changes, please document which ones ne...
12 months ago in Spectrum LSF / Administration 2 Delivered

The LSFProxy does not print a 'total' count as 'badmin perfmon view' does leading to misreading of the number of total events since restarting

In 'badmin perfmon view', we always are able to see the total events for a specific output class. This is not possible in 'badmin lsfproxyd status' output. Please add that output. Specifically, we can see average/min/max rejections from proxyd, an...
about 1 year ago in Spectrum LSF / Administration 1 Delivered

Array job maximum running jobs should be honored across multiclustered environments

Our users submit array jobs, but due to many factors may want to limit the number of running tasks at a time, not only from the source cluster, but total running jobs of that array for all clusters involved ( we have many clusters that use multicl...
over 1 year ago in Spectrum LSF / Scheduling 0 Delivered

THREAD limit to be set per HOST or PER CORE instead of PER JOB

The current THREADS limit on a queue level is set per job while it has to be set per HOST or per CORE. That is because current limit doesn't reflect the size of a job so is the THREADS limit is 600 it means that a single core job can produce up-to...
over 1 year ago in Spectrum LSF / Scheduling 2 Delivered

If 0 is given as first parameter, the bkill command ignores other options and terminates ALL jobs of the user. advise a warning if the command "bkill 0 -q gui" is used instead of the correct command "bkill -q gui 0". If tried to run, bjobs <jobid> -u <user>. The error "-u: Illegal job ID" displays. Something of this stature could be very helpful for users who do not intend to kill all their jobs.

Would it also be possible to provide documentation on what happens if the parameters are used wrong when using using "jobid 0"? Thank you.
over 1 year ago in Spectrum LSF / Documentation 2 Delivered

service classes not passed on through multi-cluster

We have a need to pass on the service classes of jobs that are attached to them from the sending cluster to the receiving cluster so we can ensure the guaranteed resource pools are using the SLA. If a sending cluster has jobs with sla's attached (...
over 1 year ago in Spectrum LSF / Scheduling 1 Delivered

Run LSF file IO operations within the container.

LSF jobs using containers depend on mounts within the container. These mounts are not available on bare metal where LSF runs file operations. The bare metal dependency means that LSF file related operations, -o, -f, -E, -Ep, etc. will not have acc...
over 1 year ago in Spectrum LSF / Scheduling 1 Delivered

provide a mechanism to avoid manually inserting hash code into thold.php and settings.php for new thold alerts to view details.

When we add our own thold alerts, we must add manually the hash code recorded into a mysql table into thold.php and settings.php scripts to be able to display details. Can you please redesign the code to avoid these steps ?
over 1 year ago in Spectrum LSF / Operations/RTM 1 Delivered

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.