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,
Post an idea
Upvote ideas that matter most to you
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.
Enabling the Smart Memory Limit conflicts with the Docker integration settings - in that, you cannot have both enabled at the same time. We believe the offending (Docker) config line is:LSB_RESOURCE_ENFORCE="cpu memory"
To enable increase in the memory for a job when overall memory resource limit is in place in lsb.resources
Case#Case number TS001621460 can be referred for this RFE. Explanation was: I have discussed with development team again, currently, LSF can not satisfy the increase memory request by bmod command for a running job when there is a general limit de...
Users need notifications when jobs are PSUSP due to pre-exec failures, and JOB_CONTROLS do not work because the job isn't RUN when it is suspended. We also need a tunable parameter to have these jobs killed after some amount of time.
almost 4 years ago
in Spectrum LSF
Not under consideration
In IBM's PMR#32285,999,760, we reported LSF can not manage Redhat7.2 gnome-terminal job.After IBM LSF support's investigation, it turns out in Redhar7.2, multiple gnome-terminal jobs share one gnome-terminal-server. To cope with this situation, a ...
Some users use a script which spawns a lot scripts, say 1000 scripts, tosubmit jobs to LSF synchronously. So a lot of jobs from this user submittedinto LSF and other users can not submit the jobs into LSF promptly with themessages of "Can not conn...
LSF to preempt tasks in a running parallel job that use borrowed resources to allow PEND jobs with guarantees to go running
We hare 3 queues.All queues have same priority.Each queue has a GRP SLA (guarantee).All queues are setup such that each queue loans out it guarantees to the other 2 queues when not used. In customer environment is often the case that 1 queue goes ...
Roll back job submission when bsub cannot receive the jobid from mbatchd
Due to a network hiccup caused by an overloaded server, job submission using bsub returned this message which of course does not include the new jobid: Failed in an LSF library call: Communication time out. Job not submitted However the job was re...
Add IBM LSF RTM alert interval by weekly basis, currently it only has daily alert notice in RTM pop-up column.
IBM Spectrum LSF RTM only have hours, daily basis of alert pop-up column could choose. For management of current alert aggregation, We need IBM to add this feature enhancement into RTM fix patch.
The features enhancement came from needs of...
Do not place IBM confidential, company confidential, or personal information into any field.