DB2 FOR LUW / DB2FORLUW / 970 - DB2

According to infocenter link : 
 
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?t 
opic=/com.ibm.db2.luw.admin.config.doc/doc/r0000339.html 
 
It states that the value of SPM_NAME is derived from TCP/IP 
hostname if not specified explicitely (i.e. Default) 
But this is not true in case of AIX but holds true for Windows. 
 
Steps to reproduce the problem : 
--------------------------------- 
 
* Login to Windows machine with any DB2 V91,V95 
* Create a new instance using db2icrt 
* db2 get dbm cfg 
 
(SPM_NAME) = < Machine_Name > 
 
i.e. it automatically takes the machine name as its default 
value which is the expected behaviour. 
 
# Login to AIX machine with any DB2 V95 
# Create a new instance using db2icrt 
# db2 get dbm cfg 
 
 
(SPM_NAME) = 
 
i.e. it is blank. 
----------------------------------- 
This APAR is applicable for db2icrt only and not for db2iupdt 
,since db2iupdt doesn't modify the dbm cfg, it won't add an 
SPM_NAME to an instance that doesn't have it.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW user referencing SPM_NAME in dbm cfg on UNIX         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* With the fix the SPM_NAME parameter in dbm cfg is set after  * 
* creating the instance with db2icrt on UNIX.                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Install V97 fp1.                                             * 
****************************************************************

Set the values of the parameter SPM_NAME manually

DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

This is fixed in V97 fp1.

not known / see Local fix

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

14.07.2009
17.02.2010
17.02.2010

9.7.FP1