DB2 DATA SRVR D / DB2DSDRVR / A10 - DB2

The SET CONNECTION, sql statement may fail with SQL0843N 
when the connection is made from IBM DS Driver Client and the 
following conditions are met. 
 
The database alias specified to SET CONNECTION statement is 
defined in db2dsdriver.cfg. 
And the values to database alias (dsn alias) and the data base 
name (name) are different. 
 
In the following example of db2dsdriver.cfg, two data source 
names, PSAMPLE and SAMPLE1 are defined. 
 
For the data source, PSAMPLE, this issue may occur because the 
character strings, "PSAMPLE" and "SAMPLE" are different. 
But this issue does not occur for the data source,  SAMPLE1 
because the same value, "SAMPLE1" is used for both the database 
alias and the database name. 
 
An example of db2dsdriver.cfg: 
 
<configuration> 
  <dsncollection> 
     <dsn alias="PSAMPLE"  name="SAMPLE" host="host.domain.com" 
port="57531"/> 
     <dsn alias="SAMPLE1"  name="SAMPLE1" 
host="host.domain.com" port="57531"/> 
 
  </dsn> 
  </dsncollection>

**************************************************************** 
* USERS AFFECTED:                                              * 
* Use using Data Server Driver                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 Fix Pack 4.                          * 
****************************************************************

Use same value to the dsn alias and the name parameters.

DB2 Version 10.1 Fix Pack 4 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.5 Fix Pack 4.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC95839 
follow-up : 

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

27.08.2013
30.06.2014
30.06.2014