This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
DB2HOST variable needed for PureScale to redirect and define IP to participating subnet's
In Db2 PureScale GDPC the Db2 cluster is distributed on 2 different physical locations and a Quorum Host (tie breaker node) on a 3rd location. The general Db2 install routines use the 'system hostname' (gethostbyname) for the ongoing install procedures. For Db2 PureScale the 'system hostname' is also forwarded to different products like Tivoli SA MP (TSAMP) and SpectrumScale (GPFS). On our environments the network infrastructure is designed to distinguish the different network locations by using different subnets. The 'system hostname' is reflecting an (relatively slow) internal network segment which is not routed to other locations. The host however can be reached by using routed other high performance networks, so called 'service network', by using a 'hostname-p1'. This network layout makes it impossible to use the TieBreaker for PureScale because DB2 enforces to use the 'system hostname' for communication. This is impossible because in our environment the 'system hostname' reflects the internal/local network, and cannot be used for communications to other plants. We require a possibility to direct DB2 using a predefined IP -Address/hostname, for example by implementing a 'DB2HOST' registry variable, so that the automatically taken 'system hostname' can be overwritten by explicitely defining a hostname/ip-address which should be used instead, and which is able to communicate to all participating subnets in all participating locations. Salesforce Ticket: TS001313467
Do not place IBM confidential, company confidential, or personal information into any field.