Author |
Message
|
WBI_user |
Posted: Wed Aug 13, 2008 8:05 am Post subject: SourceQueue name of MQGET node |
|
|
Partisan
Joined: 07 Aug 2001 Posts: 386
|
When MQInput node is used , I can pickup the Input Q name from MQMD.SourceQueue. If I wired an MQGET node in a flow MQMD.SourceQueue is not being updated.
I have a requirement to log all messages MQGETed by MQGET node with the q name used by MQGET node. Is there anyway that I can get the Q name used by MQGET node inside the flow? |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Aug 13, 2008 2:22 pm Post subject: Re: SourceQueue name of MQGET node |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
WBI_user wrote: |
When MQInput node is used , I can pickup the Input Q name from MQMD.SourceQueue. If I wired an MQGET node in a flow MQMD.SourceQueue is not being updated.
I have a requirement to log all messages MQGETed by MQGET node with the q name used by MQGET node. Is there anyway that I can get the Q name used by MQGET node inside the flow? |
Check your MQGET node. You can specify where the message goes. You may specify nothing and by default it will be OutputRoot.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
WBI_user |
Posted: Thu Aug 14, 2008 6:07 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001 Posts: 386
|
Hi fjb_saper, Do you mean that the Q name is in the outputRoot ?
I ran 2 very simple test flow with debug
Test 1.
MQInput(LQ1) - compute(copy entire msg) - MQGET( from LQ2) - compute - MQOutput
On the debug variables pane, Just before MQGET , I can see MQMD.SourceQueue=LQ1 and my input message
After MQGET , I saw MQMD.SourceQueue=LQ1 and the message (inlcude MQMD) is replaced with the message from LQ2. I scan the rest of all the variables , I cannot see LQ2 anywhere. I can not see how it can show up on the OutputRoot later?
Test 2
HttpInput - compute(copy entire msg) - MQGET(from LQ2) - compute - MQOutput
On the debug variables pane, Just before MQGET , I can see MQMD.SourceQueue= (blank) and my input message
After MQGET , I saw MQMD.SourceQueue=blank and the message (inlcude MQMD) is replaced with the message from LQ2.
So I have no idea where I can pickup the Q name that MQGET is getting the message form. |
|
Back to top |
|
 |
sridhsri |
Posted: Thu Aug 14, 2008 6:25 am Post subject: |
|
|
Master
Joined: 19 Jun 2008 Posts: 297
|
I may be sending you on a wild goose chase here....but would you mind looking up in the LocalEnvironment. I believe there is an element called destination. That could contain the queue name. |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Aug 14, 2008 1:02 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
sridhsri wrote: |
I may be sending you on a wild goose chase here....but would you mind looking up in the LocalEnvironment. I believe there is an element called destination. That could contain the queue name. |
Good advice. That was the path I was going to send you on next.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
vaibhav_vy |
Posted: Mon Aug 18, 2008 9:40 pm Post subject: |
|
|
Apprentice
Joined: 04 Aug 2008 Posts: 28
|
MQGet node populates LocalEnvironment.MQ.GET tree to indicate CC, RC & MQMD header used by MQGET call. Here the MQMD field is BLOB.
I tried to convert it into something meaningful from where I can get some information used by MQGET node. But I got errors during conversion.
Can anybody tell me how to get the details from this MQMD field ?[/quote] |
|
Back to top |
|
 |
Bill.Matthews |
Posted: Tue Aug 19, 2008 12:40 pm Post subject: |
|
|
 Master
Joined: 23 Sep 2003 Posts: 232 Location: IBM (Retired)
|
Do keep in mind that the SourceQueue field is not actually a field in the MQMD... It is in that tree for the convience of the broker code. _________________ Bill Matthews |
|
Back to top |
|
 |
WBI_user |
Posted: Mon Aug 25, 2008 10:55 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001 Posts: 386
|
Sorry, I was away for a few days. Since source queue us not part of the standard MQMD, it is probably not in the local environment. I have not tried yet. But I'll check tonight. |
|
Back to top |
|
 |
|