| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unicode and Queue Manage CCSIDs |
« View previous topic :: View next topic » |
| Author |
Message
|
| bsb36574 |
 Posted: Tue Mar 07, 2006 1:31 am Post subject: Unicode and Queue Manage CCSIDs |
 |
|
Newbie
Joined: 28 Jul 2005
Posts: 7
|
Hi,
Quick question in regards to sending Unicode data across an WMQ infrastructure.
We are trying to change our infrastructure so the end applications can send and receive "Unicode" data. We tested this by creating a queue manager on a windows machine with CCSID 1208 and sending the message to a HP-UX machine, this worked fine and the Unicode data was successfully received at the end application. But when we select "CONVERT=YES" on the server channel from the windows machine to the hub, the MQMD CCSID changes to 1051, hence the data is NOT received successfully at the end application.
In our current environment we do not have "CONVERT=YES" from most server channel connecting to the hub, apart from all server channels from AS400s are set to "CONVERT=YES" coming into the hub.
We are thinking of the following options, but would like to know what's your view on this and how you would advise we should go about this:
1. Change the hub queue manager CCSID from 819 to 1208? What's the impact of this on current applications sending in etc...
2. Create another queue manager on the hub with CCSID 1208 and that is used just for Unicode data etc.. not preferred option as this would mean creating another queue manager on the hub just for Unicode..
Appreciate any help/advise you could provide, thanks in advance.
Regards,
Bhaps |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Mar 07, 2006 2:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The convert YES is a convenience at channel level but is not intended to be heavily used. In fact the best practices encourages you NOT to use it.
You should be using instead the get with convert option when doing a GET on your message. This will ensure that a message with format MQSTR is translated into the client's CCSID and made readable.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bsb36574 |
| Posted: Wed Mar 08, 2006 3:55 am Post subject: |
|
|
Newbie
Joined: 28 Jul 2005
Posts: 7
|
Thanks for the reply.
We have a few restrictions as to why we have to convert on the sending side, one of them is we have "channel exits" on the receiving end that require the data to be "converted" prior to arrival. |
|
| 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
|
|
|
|
