| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Chinease charecters not able to find it in queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Tue Feb 25, 2014 10:50 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Mangesh1187 wrote: |
| Does it means application needs to read the message without specifying any CCSID value ? Am I correct..... |
No, it means stop asking for conversion. If you don't ask then you can specify any CCSID you want.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| zpat |
| Posted: Wed Feb 26, 2014 12:53 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Just one more point Vitor - the QMGR_CCSID does not actually mean the QM's CCSID when using the MQ client.
The CCSID used will depend on the client platform. Confused - you should be!
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Feb 26, 2014 7:05 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
For server-bindings applications, the MQMD_CCSID will be set by the qmgr to the CCSID (code page) of the qmgr.
For client-bindings applications, the MQMD_CCSID will be set by the WMQ Client to the CCSID of the client platform.
Most applications leave the MQMD_CCSID unchanged at MQPUT, and rely on WMQs built-in data conversion capabilities.
For humor value, I've seen one or two message producing applications programmatically covert its message payload to the consuming application/qmgr CCSID (rather than asking WMQ do the conversion); then overwrite the MQMD_CCSID before the MQPUT. Those were the days...
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Mangesh1187 |
| Posted: Thu Feb 27, 2014 7:01 am Post subject: |
|
|
Centurion
Joined: 23 Mar 2013
Posts: 116
|
Hi Vitor,
Your doubt was right.
Remember the flow 1st:
ABC Application (WAS)> QM1 > QM2 > QM3> MQCLNT > PQR Application (Web methods)
Today I have checked all the channels involved in this flow. And finally found that
Channel from QM2 to QM3 was having CONVERT parameter as YES.
Hence the original message (containing Chinese characters & CCSID 1208) was getting converted to CCSID , 819( QM2's CCSID ) and hence the Chinese characters were not encoded properly. And hence the PQR application was getting the error, while reading the message from the queue.
Also with this issue and all you expert comments I got now somewhat clear idea about the CCID and the its impact in MQ.
Thanks all and looking forward for your support in the future. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
