| Author |
Message
|
| sumit |
 Posted: Tue May 27, 2008 4:47 am Post subject: Difference in CCSID |
 |
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
Hi,
I am using WinXp and WMQ v6.0. The CCSID of my qmgr is set as 437. Here is a scenerio, I put a msg on a queue using explorer's "put message" option. Then I did a browse on the queue (again, in explorer). Here, I saw that the CCSID in the mqmd structure of the message is set as 1208.
I was under the impression that queue manager is responsible to handle CCSID related information. How come then the message in the queue is showing a different CCSID? Can someone please clarify. I checked the infocenter but was not able to find anything.
_________________
Regards
Sumit |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue May 27, 2008 7:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The putting application knows the content of the message and can set a different CCSID than the default on the message.
The message can come from a different environment than the one it is received in..
Etc...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sumit |
| Posted: Wed May 28, 2008 12:00 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| Quote: |
| The putting application knows the content of the message and can set a different CCSID than the default on the message. |
How can a message get a default CCSID beforehand? I am using the very much mq explorer's "put message" option. From where does the putting application (its "put message" in this case, default in explorer) get's the CCSID apart from that is set at qmgr level?
| Quote: |
| The message can come from a different environment than the one it is received in.. |
Agreed.. if the putting application would have reside on a different environment.[/quote]
_________________
Regards
Sumit |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed May 28, 2008 3:31 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The message does not get a default CCSID beforehand.
The CCSID field of the MQMD is defaulted to the AS QMGR value...
Before putting the message the app can change that and set its own value...
As well when using JMS and JNDI you can set the default CCSID for messages to be put to the queue in the JNDI layer.... and it may well not be the one of the qmgr...
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sumit |
| Posted: Wed May 28, 2008 4:02 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| Quote: |
The CCSID field of the MQMD is defaulted to the AS QMGR value...
Before putting the message the app can change that and set its own value... |
Fine, do you mean to say that the "put message" option provided by MQ explorer actually runs as a seperate process independent of qmgr and set the CCSID of the message as per message content? 
| Quote: |
| As well when using JMS and JNDI you can set the default CCSID for messages to be put to the queue in the JNDI layer.... and it may well not be the one of the qmgr... |
Agreed, I have seen these scenarios.
But just surprised, how can a qmgr base application(as in my case now) is giving a different CCSID. I mean, I am saying "put message" application again and again because I am not using any external method to put the message, its the default one. Hope I am clear enough. 
_________________
Regards
Sumit |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed May 28, 2008 8:40 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
MQ Explorer is a Java app (whence the 1208).
WebSphere MQ on distributed platforms is C (mostly) which means native.
So yes, MQ Explorer and most stuff are not part of the WMQ process.
So if you try IH03 RfhUtil (which is written in C) or just plan old amqsput or amqsputc, you will see the native CCSID. |
|
| Back to top |
|
|
|
|
