| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Structural difference between MsgId and CorrelId |
« View previous topic :: View next topic » |
| Author |
Message
|
| ghoshly |
 Posted: Mon Feb 13, 2012 10:52 am Post subject: Structural difference between MsgId and CorrelId |
 |
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Hello,
I am using Message Broker 6.0 in AIX platform. In a sample code snippet I am updating MsgId and CorrelId with the same value but the value is getting set in MsgId properly but not in CorrelId. Could you please let me know the structural difference between those two or what change I need to do in the code to populate the value in CorrelId as same as MsgId.
Code :
| Code: |
SET OutputRoot.HTTPResponseHeader = null; -- Remove HTTP Header.
SET OutputRoot.Properties.CodedCharSetId = 1208;
SET OutputRoot.Properties.Encoding = MQENC_NATIVE;
SET OutputRoot.Properties.Persistence = TRUE;
CREATE NEXTSIBLING OF OutputRoot.Properties DOMAIN 'MQMD'; -- Create MQMD.
SET OutputRoot.MQMD.Version = MQMD_CURRENT_VERSION;
SET OutputRoot.MQMD.MsgType = 2;
SET OutputRoot.MQMD.MsgId = Environment.original.MQMD.CorrelId;
SET OutputRoot.MQMD.CorrelId = Environment.original.MQMD.CorrelId;
SET OutputRoot.MQMD.Format = MQFMT_STRING;
|
The trace node output just after the compute node :
| Code: |
(0x03000000):Version = 2
(0x03000000):MsgType = 2
(0x03000000):MsgId = X'57535f5f5f5f5f5f5f5f5f476574446f63756d656e747322'
(0x03000000):CorrelId = X'000000000000000000000000000000000000000000000000'
(0x03000000):Format = 'MQSTR '
(0x03000000):Expiry = -1
(0x03000000):Encoding = 273
(0x03000000):CodedCharSetId = 1208
(0x03000000):Transactional = FALSE
(0x03000000):Persistence = 1
(0x03000000):PutDate = DATE '2012-02-13'
(0x03000000):PutTime = GMTTIME '18:20:19.240895'
(0x03000000):Priority = 0 |
Thanks in advance for helping.  |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Mon Feb 13, 2012 10:57 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 13, 2012 11:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There are any number of things that could be affecting this, including the specific fix level that you're using of Broker v6. At various times, at various levels of Broker, different parts of the message tree are used to set these IDs - sometimes Properties, sometimes MQMD.
I'd tell you to open a PMR, but you can't since you're using an unsupported level of Broker.
Nothing you've shown has provided information that can be used to help more. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Feb 13, 2012 1:06 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
In this case, the WMQ Programming Manual is your bible.
There are certain things you have to do to make WMQ (notice this is not Broker) NOT do its default behaviour and create a new MQMD.
Once you have done that, you can take those learnings into the broker world and apply them there.
Take a look and see what you would have to do it you were writing this functionality in say 'C'. Once you grasp that, making broker do it for you will be easy.
By the way, there are no structural difference between the two fields. They are both Binary fields 24 bytes long. There are many posts here about how to cast something into a BLOB.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| 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
|
|
|
|
