DB2 FOR LUW / DB2FORLUW / A10 - DB2

The System Monitor provides LIST DCS APPLICATIONS command in 
order to generate an report about applications that are 
connected to host databases via DB2 Connect. 
When using the command with option: 
1. SHOW DETAIL 
2. EXTENDED 
and when the following configuration property is set to: 
db2.jcc.enableInetAddressGetHostName=false 
the "Client node name (nname)" on the report shows truncated IP 
address, for example: 
Client node                              = 9 
instead of: 
Client node                              = 9.168.0.1 
 
The issue with truncated IP address occurs also when monitor 
snapshots is taken using the GET SNAPSHOT commands. 
 
The "db2.jcc.enableInetAddressGetHostName" configuration 
property is set to "false" by default starting with JCC driver 
version 3.65 and 4.15. 
 
To reproduce the problem: 
1. Install DB2 Connect Server and create instance. 
2. On your DB2 Connect Server catalog remote database. 
3. Enable the database server to accept client connections 
(SVCENAME, DB2COMM). 
4. Run a java program which is connecting to your DB2 Connect 
Server using connection type 4. 
5. Open DB2 Command Window and use command: 
DB2 LIST DCS APPLICATION EXTENDED 
6. Alternatively use GET SNAPSHOT commands. 
 
This APAR will address the wrong IP address output. The whole 
client node IP address will be displayed if 
db2.jcc.enableInetAddressGetHostName is set to false.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5                       * 
****************************************************************

First fixed in Version 10.1 Fix Pack 5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

20.08.2014
20.07.2015
20.07.2015