IBM Data and AI Ideas Portal for Customers

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:

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

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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Workspace Spectrum Symphony
Created by Guest
Created on Apr 22, 2020

Forcefully terminating lingering SSM and restarting on another management host

Customer largest production cluster PG1 had an incident on March 13. PG1 span over 2 ~ 3 DCs. There was a network failure between two DCs in the morning. VEMKD and SSM were running at different DCs. Customer tried to disable the app so they can restart SSM at a different management host. The action failed because SD was in process disabling SSM. SSM process was not terminated for many hours until they contact IBM. Support asked them to kill the process and then SSM could be started at another host, workload was then able to resume.

The incident was caused by network failure. But one request from customer is to enhance the feature to forcefully terminating lingering SSM and restarting on another management host.

There is a app profile parameter to do similar things. But if SSM process was hanging (for example, kill -STOP pid), EGO cannot terminate the process actually.

Description: Number of seconds to wait for the session manager to shut down before the session director considers it as timed out and restarts the session manager.
The session manager should shut down within the timeout period when the related application is unregistered or disabled.
Where used: SOAM > SSM
Required or optional: Optional
Valid values: 1 to 4294967295
Default value: 300

Need enhancement to forcefully terminate lingering SSM and restart on another management host regardless of current SSM process state.

  • Guest
    Nov 27, 2020

    .Information has been provided, to close the RFE request.

  • Guest
    Aug 12, 2020

    .Information has been provided and agreed to close this request.