| Author |
Message
|
| mark.luebinski |
 Posted: Thu Feb 08, 2007 5:19 am Post subject: CorrelID not equal to MsgID |
 |
|
Acolyte
Joined: 27 Mar 2006
Posts: 56
|
Dear Masters,
I send one message from Win2003-Integrator-Flow to z/OS-PL/1 Programm with
MQMD - MsgId = 414d5120514d43303035202020202020a5635945204ec202
and get back
MQMD: CorrelId = 414d5120514d433030332020202020202ff9c64520007e08
The colleque swears, that he copy MsgId correctly to CorrelID.
What kind of problem could it be?
Thank you very much!
Mark
Mark |
|
| Back to top |
|
 |
| zpat |
| Posted: Thu Feb 08, 2007 5:55 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Check the actual message on the first queue has the msgid that you think it should have, as it might have a freshly generated one. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Feb 08, 2007 5:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Have him write to a local queue instead of the replyto queue. Have him look at his reply message. See if the problem is there.
The first part of the IDs are the same, so if the CorrelId is an auto-generated ID, then it's being generated by the same queue manager as the MsgId.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mark.luebinski |
| Posted: Thu Feb 08, 2007 6:42 am Post subject: |
|
|
Acolyte
Joined: 27 Mar 2006
Posts: 56
|
@ zpat : I'm realy sure because I see both message in Debugger
@ jefflowrey: I asked him to make this. The first part of MessageId of the reply is REALY different from first MsgId or CorrelID.
But now I have to wait, if he make the program extension. And then I post details
Thank you very much!
Mark |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Feb 08, 2007 6:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The first part of generated IDs is the queue manager name. So it should be different for the MsgId on the reply.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Feb 08, 2007 6:46 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
The broker debugger only shows what is happening inside the broker.
You must check the queue itself to be certain that the queue manager has not assigned a new msgid on the MQPUT from the broker flow. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 08, 2007 3:20 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| zpat wrote: |
The broker debugger only shows what is happening inside the broker.
You must check the queue itself to be certain that the queue manager has not assigned a new msgid on the MQPUT from the broker flow. |
Or check LocalEnvironment tree after the MQOutput node. It should contain the MsgId and the MsgCorrelId as on the message being sent to the provider.
Note: They most certainly will be different from those on the MQMD in the broker flow debug... This means you need to map the new msg/ correlId to the MQMD before the MQGET node.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
