| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Conversion |
« View previous topic :: View next topic » |
| Author |
Message
|
| mattfarney |
 Posted: Tue Nov 22, 2011 1:57 pm Post subject: Conversion |
 |
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
When exactly does Message Broker convert the character set of an incoming message to the local QM character set?
My uneducated guess is when a non-BLOB parser is invoked, but that's just a guess.
-mf |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Nov 22, 2011 2:11 pm Post subject: Re: Conversion |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mattfarney wrote: |
When exactly does Message Broker convert the character set of an incoming message to the local QM character set?
My uneducated guess is when a non-BLOB parser is invoked, but that's just a guess.
-mf |
Well your guess is wrong as part of the assertion.
I would say never as the internal representation on the broker is in ccsid 1200 and not in the ccsid of the local QM.
Now if you set convert on the MQInput node this is a different story...
The conversion of the bitstream into the characters will happen at parsing time with a non BLOB parser... (immediate, as needed, etc...) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Nov 23, 2011 2:01 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| never as the internal representation on the broker is in ccsid 1200 |
It's actually UTF-16, which maps to 1204/1205, so the byte order of the two-byte characters will vary with the platform endian-ness. But you don't need to know or care about that when writing message flows. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Thu Nov 24, 2011 6:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| kimbert wrote: |
| Quote: |
| never as the internal representation on the broker is in ccsid 1200 |
It's actually UTF-16, ... |
or maybe UCS-2?
| kimbert wrote: |
| ... which maps to 1204/1205, so the byte order of the two-byte characters will vary with the platform endian-ness. |
Strictly speaking, ccsids describe bytes, not characters. The internal representation of characters may be similar to ccsid 1200 (or 1204/1205), but platform-dependent details such as byte order are hidden, and not directly accessible.
| kimbert wrote: |
| But you don't need to know or care about that when writing message flows. |
|
|
| 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
|
|
|
|
