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.
DB2 to support multiple network interfaces of a system in a HACMP/PowerHA cluster(RIMS)
Background of this requirement is the issue with db2nodes.cfg having IP/hostname defined different from the systems hostname, which is common definition for many customers in HACMP or PowerHA cluster. Db2nodes.cfg for the database instance gets it 'own' service address, which is moved over to the other cluster node in case of a takeover. This works pretty well during normal processing, but not for the upgrade of an instance! The upgrade process requires the nodes hostname to be stored in db2nodes.cfg. Every other IP or hostname is regarded as remote, and thus the db2iupgrade fails. Changing the db2nodes.cfg for the upgrade process is not the right way, especially if so many (several hundred) systems/instances have to be upgraded. So customer requires that DB2 supports multiple 'local' IPs/hostnames to be stored in the db2nodes.cfg. For a single partition database, every entry (there is only one!) should be regarded as local, because it has to be! Otherwise the instance could not have been used. For a DPF database the 'local' entry could be flagged, if it differs from the systems hostname. Using an alias name for the system hostname, defined in the etc/hosts file to be identical on all cluster nodes, is not an option as well, as the cluster system administration requires to have a definitions including the hosts file identical all nodes of the cluster.
Do not place IBM confidential, company confidential, or personal information into any field.