mqsistop command - Windows, Linux and UNIX systems

Purpose

Use the mqsistop command to stop a WebSphere Message Broker component.

Syntax

Parameters

Component
(Required) This must be a broker name, a Configuration Manager name, or one of the following fixed values:
  • UserNameServer or DatabaseInstanceMgr on Windows platforms
  • UserNameServer on Linux and UNIX systems

All the names are case sensitive on Linux and UNIX systems.

Do not use this command on a DatabaseInstanceMgr unless you are using the Derby database.

-q
(Optional) Stops the WebSphere MQ queue manager associated with this WebSphere Message Broker component.

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.

-i
(Optional) Immediately stop the broker.

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.

Authorization

On Windows platforms, the user ID used to invoke this command must belong to the Administrators group.

On Linux and UNIX systems, the user ID used to invoke this command must conform to the following requirements:
  • The user ID must be a member of the mqbrkrs group.
  • The user ID must either be root, or the same as that specified in the -i parameter when the component was created.
  • If you specify the -q parameter, the user ID must be a member of the mqm group.

The security requirements for using this command are summarized in Security requirements for Windows platforms and Security requirements for Linux and UNIX platforms.

Responses

  • BIP8012 Unable to connect to system components
  • BIP8013 Component does not exist
  • BIP8016 Component cannot be stopped
  • BIP8019 Component stopped
  • BIP8030 Unable to modify user privileges
  • BIP8049 Unable to stop queue manager
  • BIP8093 Queue manager being created
  • BIP8094 Queue manager stopping

Examples

Windows
To stop the Database Instance manager:
mqsistop DatabaseInstanceMgr
Windows, Linux, and UNIX systems.
To stop the broker, mybroker, and the WebSphere MQ queue manager associated with it:
mqsistop mybroker -q