| Author |
Message
|
| ivanachukapawn |
 Posted: Thu Dec 03, 2009 9:57 am Post subject: Multiple TMs |
 |
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| Attempting to debug a triggering not working scenario I want to runmqtrm -m xyz -q QL and then be in a position to see the processing of the bogus trigger message. This is on a Windows 2000 system. If there is a trigger monitor already running (which I cannot stop) this will result in 2 TMs having the same initQ open. Is there a appropriate procedure which will result in having just one TM with initQ open which I can monitor? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Dec 03, 2009 10:02 am Post subject: Re: Multiple TMs |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ivanachukapawn wrote: |
| Is there a appropriate procedure which will result in having just one TM with initQ open which I can monitor? |
If you can't stop the existing TM, and can't monitor it, then it sounds like you're a bit stuck. Any procedure which has just one monitorable TM running would seem inevitably to result in the existing one stopping. 
Unless I've misunderstood you?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 03, 2009 10:53 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
If memory serves (?), runmqtrm opens the initq INUT_EXCLUSIVE; so there's no chance of two tm's monitoring the same initq. This behavior should be easy to observe with mqsc command or MQ Explorer.
| Quote: |
| there is a trigger monitor already running (which I cannot stop) |
Why can't you stop it?
_________________
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 |
|
|
| ivanachukapawn |
| Posted: Thu Dec 03, 2009 11:07 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
the IBM MQ documentation states that I cannot stop a trigger monitor.
On another Windows XP Pro system I just started (via runmqtrm) 2 trigger monitors against the same initQ - the open input count on the initQ changed from 1 to 2 after I started the second one.
I ask this question because I wanted to be in a position to view error output from the trigger monitor but I wanted to avoid "pot luck" as to which trigger monitor was dequeuing the trigger message. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 03, 2009 11:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| the IBM MQ documentation states that I cannot stop a trigger monitor. |
Ctrl+C or some such. Also, from task monitor you should be able to cancel.
_________________
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 |
|
|
| Vitor |
| Posted: Thu Dec 03, 2009 11:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ivanachukapawn wrote: |
| the IBM MQ documentation states that I cannot stop a trigger monitor. |
Which part? Post a link.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Thu Dec 03, 2009 11:55 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 03, 2009 12:04 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ivanachukapawn wrote: |
| http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp |
Could you be a little more specific?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Thu Dec 03, 2009 12:06 pm Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
that link results in a display of this text.
When you have started a trigger monitor, it just continues monitoring the specified initiation queue. You cannot stop a trigger monitor directly. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 03, 2009 12:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ivanachukapawn wrote: |
| that link results in a display of this text. |
No, that link is the index. If you look to the left, you'll find the specific links for the specific chapters.
| ivanachukapawn wrote: |
| When you have started a trigger monitor, it just continues monitoring the specified initiation queue. You cannot stop a trigger monitor directly. |
IMHO that means you can't type STOP TRIGGER MONITOR someplace and stop it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 03, 2009 12:23 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| the IBM MQ documentation states that I cannot stop a trigger monitor. |
No, the IBM doc doesn't state that.
| Quote: |
| You cannot stop a trigger monitor directly. |
More precisely: You can stop a trigger monitor (as you can with any other process); but WMQ does not provide a control command to end the trigger monitor. It is one of those little inconsistencies we all dislike.
The trigger monitor should, for example, start with strmqtrm and end with endmqtrm; but, of course, it doesn't.
_________________
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 |
|
|
| mqjeff |
| Posted: Thu Dec 03, 2009 1:18 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
An easy way to stop a running instance of runmqtmc is to get-disable the initq, I believe.
A review of the supplied sample code for runmqtmc, which is included with all the other mq source, should give you a clearer idea of how it will behave if it gets an MQRC indicating that the INITQ is get-disabled.
I suspect this source code might also indicate how it will behave if it receives a message with MQFB_QUIT in the Feedback field of the MQMD. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 03, 2009 1:41 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
[quote...]the processing of the bogus trigger message. [/quote]
I took a look at the sample code, and it does an MQOO_INPUT_AS_Q_DEF, not INPUT_EXCLUSIVE as I speculated earlier. (Mea culpa.)
To permanently avoid subsequent trigger monitor apps monitoring the same initq, alter the initq attribute to NOSHARE.
_________________
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: Fri Dec 04, 2009 4:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqjeff wrote: |
| An easy way to stop a running instance of runmqtmc is to get-disable the initq, I believe. |
 It has been my experience that if you get disable and get enable the initiation queue in sequence the trigger monitor stops after the get disable... The get enable right after is just to not forget it... as a TM would be useless on get disabled queue...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
