The UNIX boxes belong to another group. I'll get a call sometimes from someone saying that they have sent messages to it but nothing is working. Turns out that the trigger monitor is down. Other times I'll see two trigger monitors.. If I had the interface, I could start the trigger monitor, channel initiator, command server or listener from my single, central console. It would be like having a simple, consistent (monitoring) API...
And while I can generally find my way around a UNIX boxes without bumping into too many walls, I spend most of my time on z/os and Windows. From: "Chan, Ian M" <[EMAIL PROTECTED]> on 08/29/2002 09:02 PM Please respond to MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Script showing status of MQ services - associated programs Peter, May I ask why do you want to monitor at that level? If the channels are running fine and the init queue has the open count, it should probably (although not exactly) indicate that the processes are running ok. Even with the script, you still have to log on to the unix box to fix the problem. Ian >> Now I've got all my Windows servers' MQ services on the console. Too bad I couldn't monitor the UNIX MQ services the same way. Is there an interface available??? Peter/Syracuse << 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
