| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Different Coded Character set in Queue Mgr & Queue? |
« View previous topic :: View next topic » |
| Author |
Message
|
| gertvangaever |
 Posted: Tue Apr 29, 2003 10:07 pm Post subject: Different Coded Character set in Queue Mgr & Queue? |
 |
|
Apprentice
Joined: 28 Apr 2003
Posts: 35
Location: Puurs, Belgium
|
Hello!
Working in Win2000 here, using the MMC to view Queue manager properties...
We're getting messages in a certain queue (RECEIEVE.QUEUE), in a certail queue manager (QMSC10).
It seems there's something wrong with the character set.
When I look at the message (using MMC - message browse - properties - data; like this I can view a hexadecimal version of the message), I can see two versions: the hexadecimal version seems to be (for us) incorrect: although the data should contain 'real' words, I can only see strange signs etc... When I look at the 'text' version, I can see the text that I expect to be in it, the text that was sent to the Queue.
Now what I notice is that the 'Coded character set' of the message (= of the queue?) is '37'.
When I look at the properties of the Queue Manager, the coded character set is '850'!
How is this explained?
Another issue:
In hexadecimal & text view, the data that is shown is probably the same data, but it is represented otherwise. for example '40' in hexadecimal is some weird sign, but in text mode it is a space!
Tnx... |
|
| Back to top |
|
 |
| gertvangaever |
| Posted: Tue Apr 29, 2003 10:40 pm Post subject: |
|
|
Apprentice
Joined: 28 Apr 2003
Posts: 35
Location: Puurs, Belgium
|
Is this true:
The characters (hexadecimal) stay the same, but mqseries performs a conversion (from character set 37 to 850).
The data that is read by the programmer is the HEXAdecimal data. He doesn't do a conversion, so looks at incorrect data. The solution to this is: the programmer should read the (converted) TEXT data instead of the (unconverted, of course) Hexadecimal data.
I'm not at all sure of this, so please help me!
Tnx
Gert |
|
| Back to top |
|
|
| leongor |
| Posted: Wed Apr 30, 2003 12:31 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
Yes, this is a true.
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
| gertvangaever |
| Posted: Wed Apr 30, 2003 12:36 am Post subject: |
|
|
Apprentice
Joined: 28 Apr 2003
Posts: 35
Location: Puurs, Belgium
|
We've found the solution; namely we set the CONVERT option on the channel to 'Yes'.
Is there a difference between setting a 'convert = Y' option on the channel, or setting the 'convert' option when we do a 'get message' for reading the message?
Tnx |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Apr 30, 2003 5:25 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Setting convert on a channel may lead to unnecessary or unwanted conversion attempts.
Example:
QMA sends to QMB sends to QMC. All three QMs are different CCSIDs.
An app on QMA wants to send a message to QMC, but the only connection is via QMB. If you do the conversions on your channel, then QMA is converting the message, only to give it to QMB which converts it again. This is unnecessary overhead.
The final app should specify whether they want to convert or not, and only do it once.
The convert option on channels is from the old days of MQ, when there were some QMs around that did not support conversion, so you had to convert the message before sending it. Nowadays, there is no reason I can think of to set convert yes on a channel. The apps should do it on the MQGET.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
