Author |
Message
|
AkankshA |
Posted: Mon Mar 16, 2009 8:22 pm Post subject: [Solved] kana kanji characters with trace node |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
Hi All,
I have few message flows which accept kana kanji characters.. some of the flows accept message in 943 CCSID and some in 1208.
Everything seems fine as long as the processing and DB insertion etc is concerned.
But i also use trace node for logging the message to a file. and the kana kanji characters gets converted to "^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^" in log file.
I also checked using debugger and found that the message is displayed correctly (i mean kana kanji chars) in debug mode befor the trace node and even after the trace node too. Just that the moment i write them in file.. they become junk.
Any ideas.... _________________ Cheers |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Mar 16, 2009 10:47 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Perhaps it is time to rewrite your message logging to use the fileoutput node? _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Mar 17, 2009 1:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
smdavies99 wrote: |
Perhaps it is time to rewrite your message logging to use the fileoutput node? |
While this, in general, is a good idea... specifically for *log* files, the FileOutput is not ideal. You can not use FileOutput to continuously append to a file in it's final destination. |
|
Back to top |
|
 |
Tibor |
Posted: Tue Mar 17, 2009 3:04 am Post subject: |
|
|
 Grand Master
Joined: 20 May 2001 Posts: 1033 Location: Hungary
|
AkankshA, what is your platform where the broker is running? |
|
Back to top |
|
 |
Hari |
Posted: Tue Mar 17, 2009 8:01 am Post subject: |
|
|
 Centurion
Joined: 21 Nov 2002 Posts: 117 Location: USA
|
I should say check the settings of your file editor....if possible check the hex value of the output, if it looks ok use a suitable file editor to view the trace file. |
|
Back to top |
|
 |
AkankshA |
Posted: Tue Mar 17, 2009 8:12 pm Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
Tibor wrote: |
AkankshA, what is your platform where the broker is running? |
AIX
$ uname -a
AIX ibmcl01 3 5 0005E4D4D700 _________________ Cheers |
|
Back to top |
|
 |
rekarm01 |
Posted: Wed Mar 18, 2009 3:00 am Post subject: Re: kana kanji characters with trace node |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 1415
|
AkankshA wrote: |
I have few message flows which accept kana kanji characters.. some of the flows accept message in 943 CCSID and some in 1208.
But i also use trace node for logging the message to a file. and the kana kanji characters gets converted to "^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z^Z" in log file.
Just that the moment i write them in file.. they become junk. |
When an application converts text from one ccsid to another, it often replaces characters that don't exist in the target ccsid with a substitution character, such as "^Z", (or <control>-z, or X'1A'). The trace node is converting messages to a target ccsid that doesn't include kana kanji characters.
Most likely, the target ccsid is derived from the broker's locale. (AIX uses environment variables to specify a locale for each process). The broker uses its current locale to write to the local error log, formatted usertrace files, etc. Changing the broker's locale might help. |
|
Back to top |
|
 |
AkankshA |
Posted: Tue Mar 31, 2009 4:11 am Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
I have resolved the same....
cause :
operating system did not have japanes file set
broker's ccsid was set to 819 (default for unix) _________________ Cheers |
|
Back to top |
|
 |
|