| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Interaction with MQMD.MsgId |
« View previous topic :: View next topic » |
| Author |
Message
|
| jhalstead |
 Posted: Thu Nov 29, 2001 2:23 pm Post subject: |
 |
|
Master
Joined: 16 Aug 2001
Posts: 258
Location: London
|
Having a bit of a problem here, any help or ideas would be much appreciated.
Writing an application which used the MQMD.MsgId as a unique identifier. We're translating this into hex to remove any of the more interesting characters! This works fine in UNIX, however we're experiencing problems in NT compiling with MS Visual C++.
We get the MsgId into a string and use:
sprintf(targetstring, "%02X", MQMD.MsgId[counter])
to translate each character in the MsgID one at a time and them concatenate into another string...
If we put a message on a queue using Kirans fantastic MQJExplorer the conversion will work (CCSID 819 and Encoding 273 are defaulted in the MQMD fields).
If we put a message on the queue using the standard MQSeries explorer the conversion doesn't work. (This inherits the CCSID and Encoding values of our queue manaer 473 and 546 respectively)....
I've tried re-setting the CCSID atribute of the qmgr to 819, however this doesn't seem to do the trick.
Can anyone offer any advice, does it seem reasonable to think that the CCSID of the queue manager is going to effect our conversion of the MQMD.MsgId string in our code? Are there some put or get message options we should consider?
Many Thanks
Jamie |
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Thu Nov 29, 2001 9:50 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
|
| Back to top |
|
|
| jhalstead |
| Posted: Fri Nov 30, 2001 1:37 am Post subject: |
|
|
Master
Joined: 16 Aug 2001
Posts: 258
Location: London
|
Thanks for that Roger, I'm still a little confused here. When we look at the MQMD.MsgId string in either scenarion the characters are identical (apart from the last couple where the msgid has been incremented), it's the conversion into Hex which is failing. Does it make sense that the CCSID could cause this? If so how would we perform the conversion you spoke of?
Again thanks for your help and patience.
Jamie |
|
| Back to top |
|
|
| sanjoo |
| Posted: Thu Oct 27, 2005 10:24 pm Post subject: |
|
|
Acolyte
Joined: 26 Oct 2005
Posts: 65
|
Which is the sender application platform? Mainframe?
_________________
Sanjoo
Keep smiling
 |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Oct 27, 2005 10:43 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| Which is the sender application platform? Mainframe? |
You think he's still waiting for a reply after nearly 4 years. 
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| 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
|
|
|
|
