Author |
Message
|
jkuehn |
Posted: Wed Jul 07, 2004 10:46 am Post subject: How to Batch start/stop of Trigger Monitor service |
|
|
Newbie
Joined: 17 Dec 2003 Posts: 4 Location: Halifax, Nova Scotia, Canada
|
I have reviewed the knowledge base and the Admin guide but I cannot figure this one out. Is there a way to batch script a (the) Trigger Monitor service to stop and then to start. I can do this only through MQServices Explorer at this time.
We have a TCP connection issue where connection to MQ is lost and the Server Connection Channel fails. At this point, the Trigger monitor process is still running. However the MQ Java process to take messages from a monitored queue on first appearance of a message no longer works. The Java process fails with a memory read or write exception.
We are running MQ 5.3, CSD05 which is supposed to fix the TCP connection problem but does not.
I need to stop the Trigger Monitor to clear the Open Input count, clear the messages on the Trigger initiation queue, and then start the Trigger monitor services as a manual workaround.
Can anyone tell me how to do this? _________________ John Kuehn
Senior Software Product Analyst
ITOS Systems Enablement
Maritime Life Assurance Co.
(902) 453-7307
jkuehn@maritimelife.ca |
|
Back to top |
|
 |
RogerLacroix |
Posted: Wed Jul 07, 2004 1:22 pm Post subject: |
|
|
 Jedi Knight
Joined: 15 May 2001 Posts: 3264 Location: London, ON Canada
|
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Jul 07, 2004 2:12 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
|
Back to top |
|
 |
RogerLacroix |
Posted: Wed Jul 07, 2004 2:57 pm Post subject: |
|
|
 Jedi Knight
Joined: 15 May 2001 Posts: 3264 Location: London, ON Canada
|
Hummm, scratch, scratch.
You can create a trigger monitor service with amqmdain but you cannot stop and start it!! Very strange of IBM.
Well then, the cleanest way that I can think of is to Get Inhibit the INITQ for the trigger monitor but after resetting Get Inhibit attribute, I don't know how to start it.
Maybe SupportPac MA7K will install as a regular Windows service and then you could use net start xxxx and net stop xxxxx.
Regards,
Roger Lacroix _________________ Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
Back to top |
|
 |
JasonE |
Posted: Thu Jul 08, 2004 1:31 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
As you said, there is no way to start and stop the child services of a queue manager from the command line - its something 'missing' from amqmdain, I guess. One would imagine it is the sort of thing that would be resolved in the future
Therefore the only way I can think of is to either use the support pack or srvany to produce a service, and make the service depend on the MQ service, and you can start and stop it independantly. Or to restart the trigger monitor, amqmdain end, amqmdain start the qmgr...! |
|
Back to top |
|
 |
RogerLacroix |
Posted: Thu Jul 08, 2004 8:05 am Post subject: |
|
|
 Jedi Knight
Joined: 15 May 2001 Posts: 3264 Location: London, ON Canada
|
|
Back to top |
|
 |
JasonE |
Posted: Thu Jul 08, 2004 8:47 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
You have high hopes for fixpack 8
Unfortunately fixing bugs is easier than changing product externals, so changes to published interfaces to things like amqmdain need to go through the development cycle, and wouldnt be considered for a current release... |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Jul 08, 2004 9:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
But 'bugs' are just undocumented features, right?
So if this is an unimplemented feature, it clearly can't be documented...
Which must make it a bug!  _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
RogerLacroix |
Posted: Thu Jul 08, 2004 1:07 pm Post subject: |
|
|
 Jedi Knight
Joined: 15 May 2001 Posts: 3264 Location: London, ON Canada
|
|
Back to top |
|
 |
|