IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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

Clear

Search results: Spectrum LSF

Showing 36 of 1107

Provide an Option to break out of 'bsub' if a job will not submit due to a user hitting their pending job limit

This is a major problem when using a web service to control jobs, you would much rather have the binary end with an exit code than continually block in a loop saying you have reached your pending jobs limit. It's really bad design behavior IMHO.
about 2 years ago in Spectrum LSF / Administration 0 Future consideration

Clean left over job's daemon processes after job res finished

We have several workflows that the job script can run tools that will spawn processes in the backgroup or as daemons that will stay active once the job script ends. Since the job script ends, res will end with the exit code of the job script, but ...
about 2 years ago in Spectrum LSF / Other 3 Functionality already exists

Recommended patch report code

The pversions command should have an option to output a code, like an md5sum, that enables admins to enter it in the support portal to find what patches are recommended for their server. In addition to (https://developer.ibm.com/answers/questions/...
over 6 years ago in Spectrum LSF 0 Delivered

incomplete graph legends

Can you please correct the source code of RTM for next update to have a complete legend field list for all graph (ie Cur, Avg, Min & Max) for all values ?
over 6 years ago in Spectrum LSF / Operations/RTM 2 Not under consideration

LSF should store accounting data in database

The lsb.acct log file format is anachronistic and hard for customers to deal with. To get the LSF accounting data into a relational database customers have to write their own code to parse lsb.acct files (ether via custom code such as perl/python,...
over 7 years ago in Spectrum LSF 1 Not under consideration

Prevent LSF from dispatching jobs to problematic hosts consistently

Some jobs are dispatched to a host and failed because the communication between MBATCHD and SBATCHD is failed. The host keeps in OK status and the jobs keep dispatching to the host, which makes the job can not run for a long time. The communicatio...
about 10 years ago in Spectrum LSF 2 Delivered

Use all applicable NUMA Memory information on a machine to determine available Memory resources before dispatching a job to a machine

We were noticing that jobs were being terminated by LSF with the message: TERM_MEMLIMIT: job killed after reaching LSF memory usage limit.Exited with exit code 137. Yet, this was happening before the job had even consumed the amount of memory rese...
over 2 years ago in Spectrum LSF / Scheduling 0 Planned for future release

Jobs that get into PSUSP state because they reached MAX_JOB_REQUEUE cannot be killed by an appropriate JOB_CONTROL mechanism

Answer from PMR: For the PSUSP jobs JOB_CONTROL can not work on PSUSP job. We have checked the source code in these days and found that 1. LSF doesn't set any environment variable when a job reaches its requeue limit and be put into PSUSP status 2...
about 8 years ago in Spectrum LSF 1 Delivered

blaunch to handle resized jobs

In a dynamic cluster cloud environment, blaunch cannot handle resizing of the jobs. We are requesting for the addition and deletion of hosts from an LSF cluster with blaunch able to handle the network IO and exit with the return code from the job'...
almost 3 years ago in Spectrum LSF / Cloud Bursting 1 Not under consideration

Improve Job Priority Output to Exceed 1e6 as APS can easily increase Per Job Priority above that value

There is currently a system limitation that Job Priories above 1e6 do not display correctly when using bjobs -o "blah" formatted output. This is currently causing us a monitoring issue when attempting to order jobs with a very high dynamic priorit...
about 3 years ago in Spectrum LSF / Administration 1 Not under consideration

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.