DB2 FOR LUW / DB2FORLUW / A10 - DB2

When using DRDA to connect to AS400 with VARGRAPHIC column type, 
you may get no data returned. 
Here is the reproduce steps: 
 
db2 create db fdb1 using codeset UTF-8 territory US COLLATE 
USING IDENTITY 
 
db2 catalog tcpip node inode remote ***.***.***.*** server 446 
db2 catalog database *** as idb at node inode 
 
 
CREATE WRAPPER "DRDA" 
CREATE SERVER "***" TYPE DB2/ISERIES VERSION '6.1' WRAPPER 
"DRDA" AUTHORIZATION "***"  PASSWORD "***" 
OPTIONS(COLLATING_SEQUENCE  'Y',DB2_MAXIMAL_PUSHDOWN  'Y',DBNAME 
'idb',PUSHDOWN  'Y') 
CREATE USER MAPPING FOR *** SERVER "***" OPTIONS (REMOTE_AUTHID 
'***',REMOTE_PASSWORD  '***') 
create  table test1(c1 VARGRAPHIC(10)) 
insert into test1 values('12345') 
 
create table test2(c1 varchar(10)) 
insert into test2 values('12345') 
 
db2 => select * from test1 join test2 on test1.c1=test2.c1 
 
C1                   C1 
-------------------- ---------- 
12345                12345 
 
db2 =>  select * from test1 join test2 on test2.c1=test1.c1 
 
C1                   C1 
-------------------- ---------- 
12345                12345 
 
  1 record(s) selected. 
 
 
set passthru *** 
create table testi(c1 varchar(10)) 
insert into testi values('12345') 
 
create table test1(c1 VARGRAPHIC(10)) 
insert into test1 values(VARGRAPHIC('12345')) 
set passthru reset 
 
create nickname testn for ***.***.testi 
create nickname testn1 for ***.***.test1 
 
 
db2 => select * from test1 join testn on testn.c1=test1.c1 
 
C1                   C1 
-------------------- ---------- 
12345                12345 
 
  1 record(s) selected. 
 
db2 => select * from test1 join testn on test1.c1=testn.c1 
 
C1                   C1 
-------------------- ---------- 
 
  0 record(s) selected.

User affected: 
  Users who use DRDA wrapper of  in InfoSphere Federation Server 
Problem description and summay: 
  See error description

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 fistly fixed in Version 10, FixPak 2. This 
fix should be applied on the federation Server.

keiner bekannt / siehe Local-Fix

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

18.09.2012
04.01.2013
04.01.2013