Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC64016 Status: Closed

SQL -104 (SQL0104N) WHEN USING CONTROL CENTER CONNECTING TO EBCDIC DB
ON Z/OS WITH OBJECT NAMES IN UNICODE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When using Control Center to connect to a EBCDIC database on 
Z/OS with object names in Unicode we get SQL -104 when sending 
special characters to the host: 
 
To Reproduce: 
 
1. On the Z/OS database we have a Table which name is the 
character for the Greek letter Omega in capitals: 
 
$ cat greek2 
create table ""(c int); 
$ od -cx greek2 
0000000    c   r   e   a   t   e       t   a   b   l   e       " 
            6372    6561    7465    2074    6162    6c65    2022 
cea9 
0000020    "   (   c       i   n   t   )   ;  \n 
            2228    6320    696e    7429    3b0a 
0000032 
 
0xcea9 is the Character code for ?  (Omega in capitals) 
 
db2 "select hex(name) from sysibm.systables " shows 
CEA9 
 
2. From Control Center connect to the Z/Os database and 
--> right mouse key on table schema.<omega> 
--> push down menu query: 
 
select * from schema.<omega> 
 
will show in the commend editor. 
 
If we run the above query we get SQL -104. 
 
select * from schema."<omega> " using quotes on the table name 
the query runs successful 
 
Control Center is not adding "quotes" when sending the request 
to Z/OS with special characters (it works correctly in DB2 LUW). 
 
3. Using the option Open for the table gives SQL -104 and there 
is no way of changing the request by the user in command editor.
Problem Summary:
Local Fix:
Use "" quotes to correct query in Commad Editor before sending 
to the host: 
 
select * from schema."<omega>" instead of select * from 
schema.<omega>
available fix packs:
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 6 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 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

Solution
Workaround
not known / see Local fix
Comment
using close code ISV as the rquired colse code CAN won't work
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
17.02.2010
17.02.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList