DB2 FOR LUW / DB2FORLUW / B10 - DB2

When using db2gcf to check the availability of an instance via
the following command:
db2gcf -s -i 

it may report the DB2 instance as "Operable" instead of
"Available" if a virtual hostname is used in the db2nodes.cfg
file. Here is the output of the dbgcf command in this case:

$ db2gcf -s -i db2inst1

Instance : db2inst1
DB2 State : Operable

If DIAGLEVEL is set to 4, then the following db2diag.log message
will also be observed:

2016-11-10-20.17.08.221449-300 I2895E352             LEVEL: Info
PID     : 17988                TID : 140439091885856 PROC :
db2gcf
INSTANCE: db2inst1             NODE : 000
HOSTNAME: host1
FUNCTION: DB2 Common, Generic Control Facility, gcf_getstate,
probe:2565
DATA #1 : String, 59 bytes
db2inst1 , 0 : is not local and hence status not obtained.

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 11.1 Mod1 Fix Pack 1 iFix001                  *
****************************************************************

Update the db2nodes.cfg file to contain the OS hostname value.

not known / see Local fix

forerunner  : IT17913 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

29.12.2016
01.05.2017
01.05.2017