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:

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 Db2
Components pureScale
Created by Guest
Created on Oct 11, 2016

member subset needs failback functionality without having to configure individual clients

We have a critical 2-tier application that we are trying to take to pureScale. It has thousands of DB2 clients out in the field which are difficult to configure. We want to affinitize the field clients to go to a certain member of the pureScale cluster.

We cannot use client affinity for this because it would require us to set up each client individually.

We were hoping to use "member subsets" for this. The problem with member subsets is failbacks. When the member that crashed, comes back up, the connections don't go back to that member. They persist on the surviving member.

We opened PMR 20740, 442, 000 for this but were told that in order to get failbacks working in member subset, we need to have WLB enabled.

Enabling WLB brings us back to the original problem where we would have to configure thousands of individual clients.

  • Guest
    May 23, 2019

    This is delivered as part of V11.5.0.0 GA.