| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Setting CodedCharSetId en Encoding of MQMD when using client |
« View previous topic :: View next topic » |
| Author |
Message
|
| emakaay |
 Posted: Wed Jan 18, 2006 1:16 am Post subject: Setting CodedCharSetId en Encoding of MQMD when using client |
 |
|
Newbie
Joined: 16 Oct 2003
Posts: 9
|
I'm having trouble to understand the usage of CodedCharSetId and Encoding
When I put a message on the queue I have to indicate which encoding and characterset is used. Normally I use the MQ constants MQENC-NATIVE and MQCCSI_QMGR. This makes sure that the messages are put with the encoding and message set as defined on the queue manager.
I do the same when getting a message from the queue. I use the same constants to indicate to which characterset the messages needs to be converted (to prevent questions: yes I use the MQGMO_CONVERT option)
When I have a MQ Server on windows (ASCII characterset) and I use a client on a EBCDIC platform, what values should I use for encoding en CodedCharSetId. When I use the previously mentioned constant I will indicate to put and get the message, using the client, with the wrong settings. Because the reflect the Windows queuemanager settings. Am I right ??
Other queuestion. How can the MQCCSID environment setting help in this situation
Thanks in advance,
Erik Makaay |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jan 18, 2006 4:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Where did you find a client on an EBCDIC platform? The only EBCDIC platforms that I know of are z/OS and OS/400... and neither of those have clients.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 18, 2006 6:01 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
When using a MQ Client, the CCSID is set to the CCSID of the client machine.
Jeff, MFE, a Mainframe Emulation Tool, runs on your PC and allows you to test MF code. It produduces messages in EBCIDIC, but they kept getting tagged as ASCII since the MQ Client code said "Hey, I am running on Windows!". For these scenarios, we had to specifically code MQMD_CCSID of 500 in the code. It did no harm when the code ran on the mainframe, but if forced the correct CCSID when the developers were testing on their PC.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 18, 2006 6:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
But, Peter, that's still not a client on an EBCDIC platform... 
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| emakaay |
| Posted: Wed Jan 18, 2006 11:02 pm Post subject: |
|
|
Newbie
Joined: 16 Oct 2003
Posts: 9
|
Thanks for all the replies, but the problem is fixed.
Instead of using the characterset indicated whit MQCCSI_QMGR we used (fixed) characterset 37. Now everything gets converted correctly on a get operation, and stored correctly on a put.
For Jeff, who it seems, is looking for a EBCDIC client  . We are using MQSeries for clearpath MCP. This is not really a MQ client, as described in the MQ documentation.
The question was a general question. How will the fields Encoding and CodedCharSetId when it is filled with the constant mentioned, when building a client application. Most of the time the MQ Server is running on a different platform then the client. Which normally means the characterset to be used is different |
|
| 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
|
|
|
|
