| Author |
Message
|
| mattfarney |
 Posted: Wed May 04, 2011 4:37 pm Post subject: Why is there no endmqtrm? |
 |
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
Subject pretty much says it all.
I've seen posts that say you can disable access to the initiation queue to stop it. Killing it manually is always an option.
I'm just curious why there is no endmqtrm. In a testing environment, it would be nice to be able to start and stop trigger monitors imo.
-mf |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed May 04, 2011 7:34 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
I'm guessing that it's because runmqtrm is a supplied sample application, and not a service.
_________________
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 May 04, 2011 8:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
However there is somewhere in the documentation and exemple on how to set the trigger monitor up as a service with start and stop arguments...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Thu May 05, 2011 5:02 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
Go to the InfoCenter and make a search for amqsstop , you'll get one search result, open it, server service object configured for trigger monitor.
<Though I do not get much description about amqsstop process in the mq manual other then that one liner statement.>
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| mattfarney |
| Posted: Thu May 05, 2011 8:07 am Post subject: |
|
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
| Code: |
DEFINE SERVICE(S1) +
CONTROL(QMGR) +
SERVTYPE(SERVER) +
STARTCMD('+MQ_INSTALL_PATH+bin/runmqtrm') +
STARTARG('-m +QMNAME+ -q ACCOUNTS.INITIATION.QUEUE') +
STOPCMD('+MQ_INSTALL_PATH+bin/amqsstop') +
STOPARG('-m +QMNAME+ -p +MQ_SERVER_PID+') |
The syntax +QMNAME+ is used a bunch in these sample commands.
Are those fields (+FIELD+) internally available variables that MQ is maintaining?
I assume so, since otherwise, this example is mostly useless. MQ_SERVER_PID would be painful to track and pass back in to this. 
-mf |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu May 05, 2011 10:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Easy enough to create a test service that calls echo or cat to output +MQ_INSTALL_PATH+ or etc... |
|
| Back to top |
|
|
| mattfarney |
| Posted: Thu May 05, 2011 10:30 am Post subject: |
|
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
Found my answer under
"Replaceable inserts on service definitions" -> "Common Tokens"
-mf |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu May 05, 2011 3:44 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
| I'm guessing that it's because runmqtrm is a supplied sample application, and not a service. |
runmqtrm is a supported program in the MQ binaries directory, it is not a sample application ! Maybe you are thinking of the sample trigger monitor, amqstrg.
As the prefix indicates, 'run' means that it is a potentially long running program, compared to the the 'str' and 'end' programs which are short running and only start and end other programs.
Since the introduction of MQ Service objects, the preferred method of operating a Trigger Monitor is to let the Queue Manager look after it, eg.
*
* Define a Service object for a trigger monitor on the default
* initiation queue, see http://www.ibm.com/support/docview.wss?uid=swg21284004 .
*
DEFINE SERVICE('DEFTRIGMON.SERVICE') +
DESCR('Default trigger monitor') +
STARTCMD('+MQ_INSTALL_PATH+bin\runmqtrm.exe') +
STARTARG('-m +QMNAME+ -q SYSTEM.DEFAULT.INITIATION.QUEUE') +
STOPCMD('+MQ_INSTALL_PATH+bin\amqsstop.exe') +
STOPARG('-m +QMNAME+ -p +MQ_SERVER_PID+') +
STDOUT('+MQ_INSTALL_PATH+deftrigmon-out.log') +
STDERR('+MQ_INSTALL_PATH+deftrigmon-err.log') +
CONTROL(QMGR) +
SERVTYPE(SERVER)
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu May 05, 2011 7:31 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri May 06, 2011 4:54 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| gbaddeley wrote: |
| bruce2359 wrote: |
| I'm guessing that it's because runmqtrm is a supplied sample application, and not a service. |
runmqtrm is a supported program in the MQ binaries directory, it is not a sample application ! Maybe you are thinking of the sample trigger monitor, amqstrg.
As the prefix indicates, 'run' means that it is a potentially long running program, compared to the the 'str' and 'end' programs which are short running and only start and end other programs.
|
Which sorta circles back to Matt's original question, which I too wondered about. runmqlsr has endmqlsr. Putting aside that there are better ways to control the trigger monitor and listener in MQ 7, hostorically speaking, why didn't Hursley create endmqtrm for runmqtrm? It seems like a logical requirement.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Mon May 09, 2011 6:57 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| PeterPotkay wrote: |
| gbaddeley wrote: |
| bruce2359 wrote: |
| I'm guessing that it's because runmqtrm is a supplied sample application, and not a service. |
runmqtrm is a supported program in the MQ binaries directory, it is not a sample application ! Maybe you are thinking of the sample trigger monitor, amqstrg.
As the prefix indicates, 'run' means that it is a potentially long running program, compared to the the 'str' and 'end' programs which are short running and only start and end other programs.
|
Which sorta circles back to Matt's original question, which I too wondered about. runmqlsr has endmqlsr. Putting aside that there are better ways to control the trigger monitor and listener in MQ 7, hostorically speaking, why didn't Hursley create endmqtrm for runmqtrm? It seems like a logical requirement. |
What about program to end dead letter queue handler ?
I found an old post Here (http://mqseries.net/phpBB/viewtopic.php?t=47182&postdays=0&postorder=asc&start=0&sid=d53b2e169f216b41d568741883963f72) which says about 'How to end the dlq handler' manually !
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
|
|
