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.
Currently bmod runs per job so if there are 20000 running jobs, I've to run bmod 20000 times, one for each job. Can bmod have functionality like bkill to update bulk jobs , based on certain criteria like for user, queue, hostgroup etc ?
Introduce new JOB_EXIT_TYPE to handle job failures caused by host environmental issues after job started running. Right now LSF counts environmental issues only during job initialization stage, and many problems are missed.
How to start/stop/restart Suite services on all the nodes in Suite cluster
Currently cluster admin needs to run "systemctl" for all the suite services. It's hard to remember which Suite services are running on which role of nodes in Suite cluster - different services are on master, GUI and compute nodes. So there is a n...
Hello,checking log file of RTM server, we found a recurrent warning triggered by too many job group for one of our LSF cluster. this highlight that we cannot have more than ~7000 job group for a cluster, the impacted cluster having ~30k explicit j...
Make hostgroups a valid parameter for all commands which also accept hostnames as parameter
Many LSF commands accept a hostname as parameter (bhosts, lshosts, lsload ecc.) to show the results only for the named hosts. Not all of them also accept a hostgroup as parameter (bhosts does, lshosts and lsload don't). To show the results for h...
It's about pending reason hostname.Current pending reason as below. These 3 hosts are not in host group of this queue, but they are in candidate host list. PENDING REASONS: Candidate host pending reasons (18 of 7574 hosts): Job slot limit reache...
Allow `lsadmin reconfig`to run in batch mode for only the master candidate hosts
`lsadmin reconfig` cannot be run in unattended mode only on master and master candidate hosts. It would be nice to have such an option.`lsadmin limrestart pf host1 host2` is not an acceptable replacement for this functionality. For details see "U...
Add a bjobs -R option to seach combined Resource Requirements for jobs that match a select pattern
We have been working on performing analysis of buckets in RTM, and we have found some buckets that have difficulty getting access to resources. Though we have done this, searching for jobs that match a resource requirement is proving more difficu...
Do not place IBM confidential, company confidential, or personal information into any field.