Joined: 04 Sep 2006 Posts: 197 Location: Gothenburg, Sweden
Hello,
I wonder a bit about encoding and CCSID's and the proper way to handle them.
Let say I have a .NET application which uses XMS.
Case 1
The application always sends UTF-8 encoded messages.
Case 2
The application sends different encoded messages, e.g. both UTF-8 and UTF-16.
Should the approach then be the following?
Case 1
1. Set XMSC_CLIENT_CCSID property to XMSC_CCSID_UTF8 on the ConnectionFactory
or
2. Set XMSC_WMQ_CCSID property to XMSC_CCSID_UTF8 on the destination.
Case 2
Set "JMS_IBM_Character_Set" to "1208" or "1200" depending on the message encoding.
Is that correct? _________________ Best regards
4 Integration
I wonder a bit about encoding and CCSID's and the proper way to handle them.
Let say I have a .NET application which uses XMS.
Case 1
The application always sends UTF-8 encoded messages.
So set the ccsid 1208 on your connection factory
4integration wrote:
Case 2
The application sends different encoded messages, e.g. both UTF-8 and UTF-16.
Should the approach then be the following?
Case 1
1. Set XMSC_CLIENT_CCSID property to XMSC_CCSID_UTF8 on the ConnectionFactory
or
2. Set XMSC_WMQ_CCSID property to XMSC_CCSID_UTF8 on the destination.
Realize that the destination's ccsid as set in the equivalent JNDI layer will take precedence over the connection factory CCSID.
What you're telling the qmgr, is to transform the TextMessage to the CCSID of the destination when doing the put/send.
4integration wrote:
Case 2
Set "JMS_IBM_Character_Set" to "1208" or "1200" depending on the message encoding.
Is that correct?
Set the ccsid on the message!
Luckily this will override the setting on the destination.
This may be your best bet this far for your situation.
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