Title: RE: NT/2k: trigger monitor stalls in batch window, need Enter key .
You could also use Support Pak MA7K. (Trigger Monitor Service)
 
 
 

Peter Potkay
IBM MQSeries Certified Specialist, Developer
[EMAIL PROTECTED]
X 77906

-----Original Message-----
From: DeFreitas, Nigel [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 04, 2002 3:31 PM
To: [EMAIL PROTECTED]
Subject: Re: NT/2k: trigger monitor stalls in batch window, need Enter key .

Go into the MQSeries Services and add a custom service with a start command like this: "C:/Program Files/IBM/MQSeries/bin/runmqtrm.exe -q YOUR_INIT_Q.INIT", execution: process, startup: after, startup type: automatic. This is better (than the dos option) because it starts automatically after the MQ Service starts when you reboot your servers.

 

Nigel DeFreitas

Insurance Services Office

201 469 3939

 

-----Original Message-----
From: Benjamin Zhou [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 04, 2002 1:39 PM
To: [EMAIL PROTECTED]
Subject: Re: NT/2k: trigger monitor stalls in batch window, need Enter key .

 

Rich,

thanks a lot for the info. we use v5.2.1 nt/2k with CSD5. if yours works fine, there's no reason for me to worry anymore.

best regards,
Ben

-----Original Message-----
From: Rick Tsujimoto [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 04, 2002 12:25 PM
To: [EMAIL PROTECTED]
Subject: Re: NT/2k: trigger monitor stalls in batch window, need Enter
key .

 

I have it running as a service on V5.2.1 Win/2000, CSD3 without any
problems.  I've also used it on V5.1 NT, CSD4 (I think) as well.



                      Benjamin Zhou
                      <[EMAIL PROTECTED]>          To:      [EMAIL PROTECTED]
                      Sent by:                 cc:
                      MQSeries List            Subject: Re: NT/2k: trigger monitor stalls in batch window,
                      <MQSERIES@AKH-Wi         need Enter key .
                      en.AC.AT>

 

                      11/04/2002 11:49
                      AM
                      Please respond
                      to MQSeries List




Hi Rick,

 

thanks for the reminder. What's your experiece with running trigger monitor
as service in the current version of MQ on Win2k server?

 

I had bad experience with running triggermonitor as server in version 5 on
NT a while back, when it just didn't trigger, and I can't see the cause.
Since then I just refrain from using it. It might not be justified anymore.

 

best regards,
Ben





-----Original Message-----
From: Rick Tsujimoto [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 04, 2002 11:24 AM
To: [EMAIL PROTECTED]
Subject: Re: NT/2k: trigger monitor stalls in batch window, need Enter
key.




Why not run it as a service?






                      Benjamin Zhou
                      <[EMAIL PROTECTED]>          To:
[EMAIL PROTECTED]
                      Sent by:                 cc:
                      MQSeries List            Subject: NT/2k: trigger
monitor stalls in batch window,
                      <MQSERIES@AKH-Wi         need Enter key.
                      en.AC.AT>




                      11/04/2002 10:19
                      AM
                      Please respond
                      to MQSeries List







Hi All,

 

We run trigger monitor in a batch window. Once a while, I notice it stays
there running but is not triggering, until I hit the Enter key.

 

I never experienced such problem on other platforms. So I suppose it's a
NT/2k bug. Has anyone also experienced such? is there a know solution or
trick for this?

 

thanks,

 

Benjamin Zhou
Princeton Financial.

 

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If
you are not the intended recipient, please notify the sender
immediately by return email and delete this communication and destroy all copies.

Reply via email to