Paul, Thanks for the reply. In this particular case it was a 2041 on the cluster transmit queue. I'm not sure what action I would have taken that would have altered the cluster transmit queue, but I was in the process of removing queue managers from a cluster. There were other cases, where the repository manager did restart after "600 seconds" but in some cases it did not. We are running a combination of v5.2 CSD#3 and v5.3. We had one full repository on a 5.2 qmgr and one on a 5.3 qmgr. These particular errors all occurred on the 5.2 qmgrs. In most cases, I was able to just recycle the queue managers and everything came back up fine. There are a couple, however, where I am limited by availability requirements.
Thanks John Matoba Northwestern Mutual ------------------------------------------------------------------------ ------- 07/31/02 10:25:46 AMQ9449: Repository manager restarted. EXPLANATION: The repository manager restarted successfully following an error. ACTION: None. ------------------------------------------------------------------------ ------- 07/31/02 10:25:46 AMQ9511: Messages cannot be put to a queue. EXPLANATION: The attempt to put messages to queue 'SYSTEM.CLUSTER.TRANSMIT.QUEUE' on queue manager 'YOWZAL' failed with reason code 2041. ACTION: Ensure that the required queue is available and operational. ------------------------------------------------------------------------ ------- 07/31/02 10:25:46 AMQ9409: Repository manager ended abnormally. EXPLANATION: The repository manager ended abnormally. ACTION: Look at previous error messages for the repository manager in the error files to determine the cause of the failure. ------------------------------------------------------------------------ ------- ------------------------------------------------------------------------ --------- Date: Thu, 1 Aug 2002 10:27:27 +0100 From: Paul Clarke <[EMAIL PROTECTED]> Subject: Re: Start Repository Manager? >I have a queue manager where the repository manager ended with an >AMQ9409. I waited for an hour and a half just in case it decided to >restart itself but it didn't (I can still see messages in the >SYSTEM.CLUSTER.COMMAND.QUEUE). Does anyone know a way I can restart >the repository manager with recycling the queue manager? John, A lot depends on the reason for the failure. In the error log before the AMQ9409 you should see the error message which describes the reason why the repository manager ended - for example log full, no disk space etc etc. BTW, what version of MQ are you using ? Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley 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
