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.
Most recent Linux' OS' do not provide an easy way to create a dynamic support for libnsl.so.1 any longer and instead they link to libnsl.so.2* due to libnsl.so being symbolically linked to libnsl.so.2*. The library libnsl.so.2 de-contented several...
Move away from having to set job_end_logged on every gridjobs and gridpend poller runs
The setting of job_end_logged to 0 every polling cycle can add as much as 100 seconds to every gridjobs or gridpend run. If instead, the poller were to capture the following
SELECT MAX(last_updated) FROM grid_jobs* WHERE clusterid = ?
blusers improvement to show both external and hoarding jobs in one listing
I didn't find an option in "blusers" command that will give me the full list of jobs that use specific license token. There are two options available, each gives partial picture and the output is in different format. So it takes unnecessary e...
Currently, a bmod is a very expensive activity in LSF, but running a bmod to simply change a jobs priority, should be a low impact changes. What we would request is to have the bmod that simply does an '-sp' to be handled in a way that has the lea...
Enable the Scheduler Debug to Run Continually and Provide JSON Output via 'badmin' Standard Output
Currently the Scheduler debug must be written to a file, and the scheduler debug information is not easily accessible through the management CLI. What would be better would be to have an MBD parameter to enable all the time as is done with 'badmin...
Provide "bkill -C 'some comment' jobid" Comment Message in RTM's grid_jobs and grid_jobs_finished tables
We will be doing automated killing of workload in 2022, and now that LSF provides the 'bkill -C' option, we would like that Kill message to be stored in RTM for auditing the reasons why jobs were killed by automation.
We have a high propensity to perform the following commands:
It would be good if LSF would keep track of the number of successful attempts to run those various commands as is more generally done within the 'badmi...
Based upon the data collected from the 'gridperf' binary, keep a table of events type type 'mbdreconfig' & 'mbdrestart' and present in RTM
This is important as we don't often time capture a restart or a reconfig, it could even be as a result of a binary that is segfaulting and being restarted by LIM. It would be nice to be able to track these similar to the table below:
RTM's gridparams binary misses many 'bparams -l -a' options
It's important for cross cluster auditing that the RTM system includes all 'bparams -l -a' output. Today, there are several of these options that are not captured making the auditing of cluster configuration via RTM incomplete.
Having written the...
Do not place IBM confidential, company confidential, or personal information into any field.