| Author |
Message
|
| George Carey |
 Posted: Mon Jan 12, 2009 3:08 pm Post subject: runmqdlq |
 |
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Is there a clean (er) way to stop the runmqdlq utility once it has been started with a redirected rules file input other than killing the processes.
1.)
ie at console prompt
$runmqdlq <contrl+rulesfile
would like to take down after while without needing to kill processes
did not put wait([somenumber])
2.)
Would like to see DLQ dump of reason codes in header. This util does not do it apparently ... do any of the standard IBM sample programs do this (i.e. samp/bin programs not support pacs)
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Jan 12, 2009 3:18 pm Post subject: Re: runmqdlq |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| George Carey wrote: |
Is there a clean (er) way to stop the runmqdlq utility once it has been started with a redirected rules file input other than killing the processes.
1.)
ie at console prompt
$runmqdlq <contrl+rulesfile
would like to take down after while without needing to kill processes
did not put wait([somenumber]) |
Just set the DLQ to get inhibited. It should force any DLQ handler to stop.
| George Carey wrote: |
2.)
Would like to see DLQ dump of reason codes in header. This util does not do it apparently ... do any of the standard IBM sample programs do this (i.e. samp/bin programs not support pacs) |
The DLQ handler does not dump the reason code. However you can take action depending on the reason code ex:
destq(myqueue) reason(2053) action(retry)
Remember to end the rules file on a blank line. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| George Carey |
| Posted: Mon Jan 12, 2009 3:32 pm Post subject: dlq reason codes break out |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
| Quote: |
Just set the DLQ to get inhibited. It should force any DLQ handler to stop.
|
Great good tip for 1 will try.
On 2 ... understood on reason code actions taken but what I am looking for is interrogation after the fact as to why the Message was put to DLQ without going to Hex break out in words whatever 5 and 6 or something like that.
Also where the heck is the source for amqsdlq ?? can't find in /opt/mqm/samp ??
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| George Carey |
| Posted: Mon Jan 12, 2009 3:38 pm Post subject: tip on 1 |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Tip 1 get (disable) on DLQ works like a champ !!
Thnks !
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jan 12, 2009 3:58 pm Post subject: Re: dlq reason codes break out |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| George Carey wrote: |
On 2 ... understood on reason code actions taken but what I am looking for is interrogation after the fact as to why the Message was put to DLQ without going to Hex break out in words whatever 5 and 6 or something like that.
Also where the heck is the source for amqsdlq ?? can't find in /opt/mqm/samp ?? |
Have you tried MO71? Look at the messages in the DLQ. You should see the reason code in readable format... The same with RFHUtil(c)... (last tab on the right is the DLQ tab)...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| George Carey |
| Posted: Mon Jan 12, 2009 4:12 pm Post subject: support pacs |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Was hoping to avoid using support pacs ... a hassle getting other than direct product components in the environment.
As an interim ... where/what is the Hex breakout for reason code in DLQH again .... word 5 or 6 or something like that ?
Thanks for feed back will work to get support pacs in meantime. Also no windows code options.
rgds
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jan 12, 2009 4:16 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| George Carey |
| Posted: Mon Jan 12, 2009 5:04 pm Post subject: found this snippet |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
from a google search:
| Quote: |
to find the reason code is a little bit difficult:
the message text begins with
00000000: 444C 4820 0000 0001 0000 0827 4C54 522E 'DLH .......'LTR.'
This is the beginnig of the Dead Letter Header=DLH (described in the WMQ Application Programming Reference).
The third word is the reason code: "0000 0827", it is in hex code and means 2087 = MQRC_UNKNOWN_REMOTE_Q_MGR .
|
So if true it is third word ... I will see if this is true..
on
the MQFB is for MQ Feed Back not reason code but sometimes does give the actual reason for DLQ placement but not sure what the post means otherwise ??
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jan 12, 2009 6:05 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Certain programs, maybe not runmqdlq, will use a message received with MQFB_QUIT as a signal to... you know... quit. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 13, 2009 2:16 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The other way is to add to the first line in the dlq handler file
wait(no)
1st line can only contain stuff like
inputq(DLQ) inputqm(QMGR) wait(no)
You can overwrite the inputq and inputqm from the command line...
This makes sure that once the DLQ has been gone through the handler stops. It doesn't however prevent from looping if the message gets back to the DLQ before the handler is done...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| George Carey |
| Posted: Tue Jan 13, 2009 4:53 pm Post subject: item 1 covered but item 2 not |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
I will have to experiment with wait(no) ...
Of my two questions , the first(1) has been answered quite well ...
Tip in particular for clean way to stop runmqdlq after the fact was good.
Item 2 was one I was looking to get a standard samp/bin program to give me a way to break out RC.
It would be nice if runmqdlq had a list action that just dumped Reason codes of DLQ messages ... something like:
wait(no)
action(list) or action(listRC) something like that ....
The little word 3 break out was correct a staight hex -> decimal conversion.
But not too good if more than a few messages in DLQ. I suppose a handy dandy script could be coded up to break it out.
Item 2 again was
| Quote: |
| Would like to see DLQ dump of reason codes in header. ... |
On,
| Quote: |
Certain programs, maybe not runmqdlq, will use a message received with MQFB_QUIT as a signal to... you know... quit.
|
was this an item 1 answer?
If so, as a clean(er) way to stop runmqdlq as described, how would one use it in the item 1 case given??
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| xhaxk |
| Posted: Tue Jan 13, 2009 9:54 pm Post subject: |
|
|
Apprentice
Joined: 30 Oct 2008
Posts: 31
|
| the source of runmqdlq is not issued, but there is sample dlq handler source supplied. i cannot remember what it is called. |
|
| Back to top |
|
|
| George Carey |
| Posted: Tue Jan 13, 2009 10:07 pm Post subject: sample |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Example module is amqsdlq I believe but I could not find source for it in /opt/mqm/samp directory either ??
Saw some cryptic doco saying amqsdlq source pulled from several areas ... what ever that means ??
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Tue Jan 13, 2009 11:19 pm Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
$ ps -ef | grep runmqdlq
----
---
Note the PID of runmqdlq
$ kill -9 PID |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Jan 14, 2009 2:52 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| aditya.aggarwal wrote: |
$ ps -ef | grep runmqdlq
----
---
Note the PID of runmqdlq
$ kill -9 PID |
A sledgehammer to crack a nut - note fjb_saper's suggestion, which is a 'cleaner' way to do it.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
|
|
