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 Jun 6, 2018

Db2 GDPC pS missing RsCT condition

In pureScale GDPC environment, RsCT condition for bond0 missing after enter/exit maintenance mode.

PMR suggested details:
"1) when "db2cluster -cm -enter -maintenance" was run, it ran the script condrespV111_setup.ksh to delete all conditions/responses for bond0 and bond2

2) when ""db2cluster -cm -exit -maintenance" was subsequently run, it call the script again to recreate those conditions/responses, however the script only recreated the conditions/responses for the adapters for "subnets" in mmlsconfig (bond 2) , not the other interface (bond 0).

3) According to below our script condrespV111_setup.ksh, it does show that our script only creates condition for the adapter which is in the subnet as mmlsconfig output, and unless no such adapter is found, no condition will be created for other adapters.

However in your case, you have conditions/responses created for both the private adapter as in subnet (bond 2) and also the public adapter(bond0).

Currently only the Spectrum Scale heartbeat interface is used to create condition/response pairs. In GDPC's case, both of the public ethernet network and Spectrum Scale heartbeat interface(bond 2 and bone 0 respectively) are used to create the cond/resp pair.

However currently such pairs are created by the condresp setup script for the Spectrum Scale heartbeat interface, and the condresp pairs needs to be configured manually for the public ethernet.

The existing behavior of the script condrespV111_setup.ksh is meant for the adapter which is in the subnet as mmlsconfig output.

Can I request you to raise RFE (request for enhancement) so that the script condrespV111_setup.ksh will take care of public ethernet network?"
  • Guest
    May 23, 2019

    This is delivered as part of V11.5.0.0 release.