| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Bidirectional text in the queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| hooman24 |
 Posted: Wed Aug 26, 2020 4:35 am Post subject: Bidirectional text in the queue |
 |
|
Apprentice
Joined: 09 Aug 2014
Posts: 25
|
We are trying to insert Bidirectional text into a queue(Arabic+English). Content in Arabic which is RTL includes an inline English phrase which is in the opposite direction(LTR).
I didn't find any property in the queue or qmgr to force direction. It seems application programs could dictate text direction. Using MQ explorer to put/browse message always result bad shape message. Is there any way to force all messages to be Right-To-Left? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Aug 26, 2020 6:38 am Post subject: Re: Bidirectional text in the queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hooman24 wrote: |
| I didn't find any property in the queue or qmgr to force direction. |
Because neither the queue manager nor the queue care about direction. They are mostly blind to message content unless you explicitly set the descriptor to indicate it's a string, when in some circumstances they'll translate character set.
| hooman24 wrote: |
| It seems application programs could dictate text direction. |
They could and should.
| hooman24 wrote: |
| Using MQ explorer to put/browse message always result bad shape message. |
MQ Explorer is just displaying the message contents. It really doesn't care about direction any more than the queue or the queue manager does.
| hooman24 wrote: |
| Is there any way to force all messages to be Right-To-Left? |
No, because as I've tried to explain above, messages don't have a concept of direction and really don't have much of a concept of text.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| hooman24 |
| Posted: Wed Aug 26, 2020 8:46 am Post subject: |
|
|
Apprentice
Joined: 09 Aug 2014
Posts: 25
|
Thank you vitor for your nice clarification.
So if I understand correctly, because message is not a text ,we cannot manipulate it like a string. However programmer can add some message description to add extra behavior to it(This message is a string and should be RTL), and application can browse this message and read description and realize this message is a RTL string.
So If I'm right, it is better that the message producer put correct formatted string into the queue so consumer can read.
The main point here is that MQ will NOT change format of input message AT ALL. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 26, 2020 9:34 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| hooman24 wrote: |
Thank you vitor for your nice clarification.
So if I understand correctly, because message is not a text ,we cannot manipulate it like a string. However programmer can add some message description to add extra behavior to it(This message is a string and should be RTL), and application can browse this message and read description and realize this message is a RTL string.
So If I'm right, it is better that the message producer put correct formatted string into the queue so consumer can read.
The main point here is that MQ will NOT change format of input message AT ALL. |
Depending on the target system (really more target ccsid) and type (windows vs Unix/ Linux) you may see changes in a "String" formatted message (MQFMT_STRING). Mostly the EOL (end of line) changing from x0d0a to x0a only or vice versa.... This is expected behavior. You may also have a conversion between EBCDIC and ASCII or UTF-8 etc... That too is expected behavior... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 26, 2020 11:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hooman24 wrote: |
| So if I understand correctly, because message is not a text ,we cannot manipulate it like a string. However programmer can add some message description to add extra behavior to it(This message is a string and should be RTL), and application can browse this message and read description and realize this message is a RTL string. |
Yes, using markup or similar at their discretion.
| hooman24 wrote: |
| So If I'm right, it is better that the message producer put correct formatted string into the queue so consumer can read. |
Especially if (as you indicated in your original post) you have a mixture of LTR & RTL in the same message. Parsing that without hints from the producer is going to be a lot of work.
| hooman24 wrote: |
| The main point here is that MQ will NOT change format of input message AT ALL. |
As I and my worthy associate have mentioned, if the message is tagged by the sender as being MQFMT_STRING and the necessary code page conversion table is available to the queue manager and the consumer explicitly requests it from the queue manager, then the queue manager will attempt a simple code page conversion as my associate describes.
If any of these conditions are not met, the message payload will be delivered unchanged. So for example, if there is a conversion table available and the consumer requests that conversion is performed, a message with a format of MQFMT_NONE will be delivered unchanged.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| hooman24 |
| Posted: Thu Aug 27, 2020 5:57 am Post subject: |
|
|
Apprentice
Joined: 09 Aug 2014
Posts: 25
|
| Thank you Vitor and fjb_saper for your help. |
|
| 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
|
|
|
|
