Stopping a queue manager manually

The standard way of stopping queue managers, using the endmqm command, should work even in the event of failures within the queue manager. In exceptional circumstances, if this method of stopping a queue manager fails, you can use one of the procedures described here to stop it manually.

Stopping queue managers in WebSphere MQ for Windows

To stop a queue manager running under WebSphere MQ for Windows:

1. List the names (IDs) of the processes currently running using the Windows Process Viewer (PView)
2. Stop the processes using PView in the following order (if they are running):
   

   AMQPCSEA.EXE	The command server
   AMQHASMN.EXE	The logger
   AMQHARMN.EXE	Log formatter (linear logs only)
   AMQZLLP0.EXE	Checkpoint process
   AMQZLAA0.EXE	LQM agents
   AMQZFUMA.EXE	OAM process
   AMQZTRCN.EXE	Trace
   AMQZXMA0.EXE	Execution controller
   AMQXSSVN.EXE	Shared memory servers
   AMQRRMFA.EXE	The repository process (for clusters)
   AMQZDMAA	Deferred message processor

3. Stop the WebSphere MQ service from Services on the Windows Control Panel.
4. If you have tried all methods and the queue manager has not stopped, reboot your system.

Stopping queue managers in WebSphere MQ for UNIX systems

To stop a queue manager running under WebSphere MQ for UNIX systems:

1. Find the process IDs of the queue manager programs that are still running using the ps command. For example, if the queue manager is called QMNAME, use the following command:

   ps -ef | grep QMNAME
   

2. End any queue manager processes that are still running. Use the kill command, specifying the process IDs discovered using the ps command.

   End the processes in the following order:
   

   amqpcsea	Command server
   amqhasmx	Logger
   amqharmx	Log formatter (linear logs only)
   amqzllp0	Checkpoint processor
   amqzlaa0	Queue manager agents
   amqzfuma	OAM process
   amqzxma0	Processing controller
   amqrrmfa	Repository process (for clusters)
   amqzdmaa	Deferred message processor

If you stop the queue manager manually, FFSTs might be taken, and FDC files placed in /var/mqm/errors. Do not regard this as a defect in the queue manager.

The queue manager should restart normally, even after you have stopped it using this method.