| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| HELP!!! SELECT using special characters |
« View previous topic :: View next topic » |
| Author |
Message
|
| RPGranzotto |
 Posted: Wed Jul 21, 2004 5:38 am Post subject: HELP!!! SELECT using special characters |
 |
|
Newbie
Joined: 22 May 2002
Posts: 4
Location: São Paulo, Brazil
|
I have a problem.
I'm working in a project implementing WBIMB version 5.0 in Spain. We are using tables located in the DB2 database to perform the translation of some field values in the incoming message.
The problem we are experiencing occurs when making a SELECT using a value as a key field that contains special characters (an "Ñ" for example), the seacrh result is 0 registers but there are values to return in the database. The other problem occurs when a SELECT returns a value that contains a special characters, in this case we are obtaining the following WBIMB exception ("UNCONVERTABLE CHARACTER" "COD 2135").
The Broker and DB2 database are runing in the same Solaris Server.
The messages have the CCSID parameter set in 819 in the MQMD (Solaris Code). The messages are interpreted correctly (the parsing process works). I'm executing the query (SELECT) with a PASSTRHU statement. In those cases without special characters, it works correctly.
Is there are additional configuration to make (In DB2 or ODBC, for example) in order to make it work?
I also tested the SELECT statement with harcoded values in the Key Field (for example "ESPAÑA"), and in the ODBC trace file it appears as "ESPAÃA".
I also tested in:
- Client DB2 in Windows environment (Command Center), and it worked.
- Client DB2 in Solaris environment (Command Center). It works, but it changes the special character ( example: ESPAÑA to ESPA#A).
Any idea. PLEASE HELP ME !!!!
I hope my english is clear enough to depict the problem
Ricardo Paino Granzotto
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
 |
| RPGranzotto |
| Posted: Fri Aug 20, 2004 12:29 am Post subject: Solved! |
|
|
Newbie
Joined: 22 May 2002
Posts: 4
Location: São Paulo, Brazil
|
Hi all.
Solved the problem.
What it happens is that the WBIMB always that access makes transaction involving the DB, uses as code page UTF-8 (unicode). And this code page was not configured for the users who execute the accesses.
As solution we had that:
- Modify the archives ".profile" of the users of WBIMB and DB2, adding to them variables referring the language control and code page.
- export LANG=es_ES
- export LC_ALL=es_ES.UTF-8
- export LC_LANG=es_ES
- export LC_COLLATE=es_ES.UTF-8
- export LC_CTYPE=es_ES.UTF-8
- export LC_MESSAGES=es_ES.UTF-8
- export LC_MONETARY=es_ES.UTF-8
- export LC_NUMERIC=es_ES.UTF-8
- export LC_TIME=es_ES.UTF-8
It was not necessary to modify nothing in the message flows, nor in the configurations of tools WBIMB and DB2.
"SALUDOS"
Ricardo Paino Granzotto
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
