Use the mqsistop command to stop a WebSphere Message Broker component. On z/OS, the controller must be running.
Component | Command | Description |
Broker |
|
|
Configuration Manager |
|
|
User Name Server |
|
|
Do not use this command on a DatabaseInstanceMgr unless you are using the Derby database.
Specify this flag only if the WebSphere Message Broker component is the last (or only) WebSphere Message Broker component active on this queue manager. This command initiates a controlled shutdown of the queue manager, and informs other users of the queue manager that it is closing.
If you do not stop other WebSphere Message Broker components that use this queue manager before you issue this command with this option, stop them afterwards or restart the queue manager.
If you use this option, be aware that any listeners associated with this queue manager are not stopped with the queue manager. Stop these manually after issuing this command.
Only specify this flag if you have already tried, and failed, to stop the broker in a controlled fashion using mqsistop without the -i flag.
On z/OS this command will be rejected by the Message Broker console command server if a previous stop command has failed to complete. This can occur, for example, if one or more execution group address spaces cannot shutdown.
On Windows platforms, the user ID used to invoke this command must belong to the Administrators group.
The security requirements for using this command are summarized in Security requirements for Windows platforms and Security requirements for Linux and UNIX platforms.
mqsistop DatabaseInstanceMgr
mqsistop mybroker -q
F MQ00BRK,pc
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an07240_ |