| Author |
Message
|
| Capcop |
 Posted: Tue Jan 11, 2005 9:57 am Post subject: Source Qmanager???? |
 |
|
Novice
Joined: 27 Jul 2004
Posts: 17
|
I' have problem,
--->[QM1] --->
--->[QM2] ---> [BROKER]
--->[QM3] ---> [QMBROKER]
--->[QM4] --->
as I can to know the origin of where the message came?
I need to know if it stores it in some structure of the message
thanks for the aid
_________________
---------------
Capcop IEE |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Tue Jan 11, 2005 10:29 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
with any luck and the broker just passes the MQMD you should find the original source Qmanager name in the reply-to-queuemanager field in the MQMD.
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| Capcop |
| Posted: Tue Jan 11, 2005 12:41 pm Post subject: |
|
|
Novice
Joined: 27 Jul 2004
Posts: 17
|
mmm 
the MQMD I occupy it for which you say to me your, and it works perfect
The problem he is that now the client connects itself with *, instead of the name Qmanager, so that it must be connected to by defect, for that reason not to as I connect myself
in summary, I need to know the origin of Qmanager, to replace * of RepleyToQmanager
thanks
_________________
---------------
Capcop IEE |
|
| Back to top |
|
|
| RAJESHRAMAKRISHNAN |
| Posted: Mon Jan 24, 2005 10:02 pm Post subject: |
|
|
Voyager
Joined: 01 May 2004
Posts: 96
|
I guess you need to find the Queue Manager from where the message originated, Right?
In that case, you can find the original queue manager from the first 12 chars in Hex (Please cross check this number) of the message Id. |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Jan 24, 2005 11:20 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
It's better to have the source application set some field in MQMD header. For example, MQMD.ApplIdentityData or MQMD.ApplOriginData.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| JT |
| Posted: Tue Jan 25, 2005 9:34 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| RAJESHRAMAKRISHNAN wrote: |
In that case, you can find the original queue manager from the first 12 chars in Hex (Please cross check this number) of the message Id.
|
Not sure this statement is true, since queue manager names can be up to 48 characters in length. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 26, 2005 4:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| JT wrote: |
| RAJESHRAMAKRISHNAN wrote: |
In that case, you can find the original queue manager from the first 12 chars in Hex (Please cross check this number) of the message Id.
|
Not sure this statement is true, since queue manager names can be up to 48 characters in length. |
It's certainly not guaranteed to be true, since it is not guaranteed that the queue manager will generate the message ID - as that is up to the programmer.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 26, 2005 6:23 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You will never have a 100% sure way of knowing where the message originally came from, nor should you care. That is the point of MQ - both sides don't care about the other - its asynchronous.
Why do you want to know what the original QM is?
If its because you need to send back a reply, then Michael had the right answer - look in the ReplyToQueueManager field of the MQMD.
If the applications in between the original sending QM and your apps changed that field, its their fault, not yours or MQ's fault.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
