Hi Rob, Looks like the problem went away. All I did was make the startup processes manual. Tried to delete the unused dynamic queues. Was not able to delete them because they were in use. Anyway, once all this was done, I was able to view all the queues using MQExplorer and there was no problem. Now I told the MQ admins on that machine to set everything back to automatic. And looks like everything is working fine.
Thanks a lot for the help everyone. Really appreciate the way that everyone on this list helps out a person. Way to go! Thanks Aby Philip -----Original Message----- From: Wyatt, T. Rob To: [EMAIL PROTECTED] Sent: 12/12/02 5:00 PM Subject: RE: Help needed..MQExplorer not showing queues on production Ok. In that case, I still favor turning on events and see if any are generated. If, as others have suggested, it is an authority problem, this will generate an event. On the other hand, if the connection is being refused for some reason, a different event will show up. -- T.Rob -----Original Message----- From: Philip, Aby [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 3:38 PM To: Wyatt, T. Rob Subject: RE: Help needed..MQExplorer not showing queues on production Hi Rob, The SYSTEM.ADMIN.COMMAND.QUEUE has a depth of 0. I can see the queues while using runmqsc, and like Nick said see if any dyn queue are damaged. Thanks -----Original Message----- From: Wyatt, T. Rob To: [EMAIL PROTECTED] Sent: 12/12/02 3:29 PM Subject: Re: Help needed..MQExplorer not showing queues on production Philip, The Channel Initiator starts automatically in newer versions of MQSeries. When you start it again, the new instance can't open the queue for exclusive input because the old instance already has it, hence the error. As for the MQExplorer, do you have a SYSTEM.ADMIN.COMMAND.QUEUE defined? If so, are the messages being consumed or is the queue depth building as you exercise the explorer? Are there dynamic reply queues laying around after explorer fails? Finally, have you turned on the performance, qmgr and local events? If you are getting past the listener, failures should produce some event messages that tell you what's happening. -- T.Rob -----Original Message----- From: Philip, Aby [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 2:51 PM To: [EMAIL PROTECTED] Subject: Help needed..MQExplorer not showing queues on production Hi everyone, I have a serious problem here. I am able to see a queue manager (remotely connecting) but not the queues. I went to the local machine and used MQExplorer on it and the same problem occurs there. I am able to view the queue manager and not the queues. I get the error "Timed out". Check the SYSTEM.ADMIN.COMMAND.QUEUE. Error code AMQ 4303. Command server is not started. The command server is started and queue manager is running. We were not able to shut down the command server before. It was giving error AMQ8101 but no reason code. So then I changed the queue manager, command server, channel initiator, and listener to manual startup. And shut down the machine and started it up again. This time I ran runmqlsr, strmqm, strmqcsv in that order. When I tried running the runmqchi I get the error code AMQ9505, could not open queue or queue manager object. Permissions to everything is present as I am logged in as administrator. Any pointers anyone? Thanks for the help. Aby Philip 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 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
