Skip to Main Content
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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Workspace Db2
Components pureScale
Created by Guest
Created on Aug 12, 2015

Remove timeout for member stop when applying fixpacks to pureScale

The installFixpack for pS automatically stops and starts the member or CF. But before stopping it waits for applications to finish their existing work and drain all connections on this member and start new work to other surviving members. If any application is performing a long-running transaction (more than 20 mins), the transaction will be allowed to finish and installFixpack will timeout.

This is the current process for applying a fixpack. We feel that the stopping of the member should be manually managed and not by the script. The problem with the current process is
# a stop member is issued and must complete or time out for the fixpact script to continue. If the Apply fails before stop is completed, the stop is still pending.
# In a busy/ production system, a wait of 20 minutes is too long to find out that you cant stop the member. Even though other members are up, there is still a reduced capability of the pureScale environment till the fixpack is applied.