| Author |
Message
|
| dev135 |
 Posted: Wed Sep 28, 2011 11:06 am Post subject: |
 |
|
Apprentice
Joined: 21 Oct 2008
Posts: 44
|
I am using MO71 new version 7.0.2 ,say if i got a message to my DLQ, when i look up for the destination queue in the MQMD header , the queue name is being displayed as AAA.BBB.C.DD.00 instead of correct queue name AAA.BBB_C_DD.00 (which i could see thru old version of MO71) .
Did any one faced this issue ? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Sep 28, 2011 11:22 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| dev135 wrote: |
I am using MO71 new version 7.0.2 ,say if i got a message to my DLQ, when i look up for the destination queue in the MQMD header , the queue name is being displayed as AAA.BBB.C.DD.00 instead of correct queue name AAA.BBB_C_DD.00 (which i could see thru old version of MO71) .
Did any one faced this issue ? |
This is quite standard
You need to run a DLQ handler on your DLQ.
From memory the rule should look something like this:
| Code: |
wait(no)
destq(AAA.BBB.C.DD.00) action(forward) fwdqm(&destqm) fwdq(AAA.BBB_C_DD.00) header(no)
|
And notify the sender to fix his destination.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Sep 28, 2011 11:30 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I think he's trying to report a change in MO71.
I would be surprised if MO71 changed characters in the MQMD or displayed them differently.
Have you looked at the same DLQ message in both the old and new version of MO71? |
|
| Back to top |
|
|
| dev135 |
| Posted: Wed Sep 28, 2011 12:44 pm Post subject: |
|
|
Apprentice
Joined: 21 Oct 2008
Posts: 44
|
Yes zpat ...i am referring the characters being changed on queue name in MQMD header of new version of MO71.
Have you looked at the same DLQ message in both the old and new version of MO71? Yes i did , its displaying the correct destination queue name (in MQMD header) with right characteristics in old version of MO71. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Sep 28, 2011 1:29 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Use amqsbcg or some other utility to look at the hex-equivalent to see if the queue name is correct.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| dev135 |
| Posted: Wed Sep 28, 2011 4:49 pm Post subject: |
|
|
Apprentice
Joined: 21 Oct 2008
Posts: 44
|
| well, i do know there are other utlities, i am just trying to find if any one has faced this issue while using new version of MO71 and if there is any fix or something . |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Sep 28, 2011 5:05 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Since nobody seems to have encountered your results, I thought I'd ask you to try to determine exactly where the queue name is corrupted. In the supportpac or elsewhere?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Sep 28, 2011 8:56 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If the reason code on the DLQ is 2085 it may well be that the queue name was not set right at the beginning, or was changed somewhere on the way (qr) to the wrong value. That would then be why the msgs are in the DLQ.
I don't know that MO71 would be displaying the original queue name differently than what it is set on the DLQ header of the msg.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Sep 28, 2011 10:10 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| If you are sure, why not copy/unload the message (using MO71 and keeping the DLH) and send it to Paul Clarke along with some screen shots. |
|
| Back to top |
|
|
| dev135 |
| Posted: Thu Sep 29, 2011 9:17 am Post subject: |
|
|
Apprentice
Joined: 21 Oct 2008
Posts: 44
|
@zpat
I already sent an email to Paul. Waiting for response. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Sep 29, 2011 9:22 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| dev135 wrote: |
I am using MO71 new version 7.0.2 ,say if i got a message to my DLQ, when i look up for the destination queue in the MQMD header , the queue name is being displayed as AAA.BBB.C.DD.00 instead of correct queue name AAA.BBB_C_DD.00 (which i could see thru old version of MO71) .
Did any one faced this issue ? |
As a further test, reinstall the old MO71 to see if the queue name is displayed correctly.
fjb_saper's post was asking you to look at the QRemote definition that the application opened. What exactly is the RName? Is it spelled correctly? It is the RName field that populates the XQH used to ship the message down the network; and it is the RName filed that is used to populate the DLH.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
