DB2 FOR LUW / DB2FORLUW / A10 - DB2

When DB2 Remote Command Server Service starts up in Windows 
environment, 
a meaningless event record might be logged in Windows 
Application Event Log. 
 
The following is an example of the event record in XML format. 
 
<Event 
xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> 
 
  <System> 
 
    <Provider Name="DB2REMOTECMD_DB2COPY1" /> 
 
    <EventID Qualifiers="49152">1</EventID> 
 
    <Level>4</Level> 
 
    <Task>0</Task> 
 
    <Keywords>0x80000000000000</Keywords> 
 
    <TimeCreated SystemTime="2011-11-09T13:26:00.000000000Z" /> 
 
    <EventRecordID>12762</EventRecordID> 
 
    <Channel>Application</Channel> 
 
    <Computer>mycomputer.ibm.com</Computer> 
 
    <Security /> 
 
  </System> 
 
  <EventData> 
 
    <Data>rcmdTcpipListener</Data> 
 
    <Data>Failed to configure listener's socket address. Check 
for 
port (db2ccmsrv) in SERVICES file, rc = 118423736.</Data> 
 
    <Data> 
 
    </Data> 
 
    <Data> 
 
    </Data> 
 
    <Data> 
 
    </Data> 
 
    <Data> 
 
    </Data> 
 
    <Data> 
 
    </Data> 
 
    <Data> 
 
    </Data> 
 
    <Data> 
 
    </Data> 
 
    <Data> 
 
    </Data> 
 
  </EventData> 
 
</Event> 
 
The customer can ignore the above record safely.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows environment only.                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V10.1 Fix Pack 1.                                 * 
****************************************************************

The user can disable auto start-up of DB2 Remote Command Server 
Service if it is not used.

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 1.

not known / see Local fix

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

14.06.2012
01.11.2012
01.11.2012