WebSphere Message Brokers
File: an28080_
Writer: Bill Oppenheimer

Reference topic

This build: July 31, 2007 21:34:07

mqsistop command - Windows, Linux, and UNIX systems

This topic shows you how to use the mqsistop command onWindows, Linux, and UNIX systems.

Purpose

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

Syntax

Parameters

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

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

Do not use the mqsistop 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. The mqsistop command initiates a controlled shutdown of the queue manager, and informs other users of the queue manager that it is closing.

Stop other WebSphere Message Broker components that use this queue manager before you issue the mqsistop command with this option; alternatively 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 the mqsistop command.

-i
(Optional) Immediately stops the broker.

Only specify this flag if you have already tried, and failed, to stop the broker in a controlled fashion using the mqsistop command without the -i flag.

Authorization

Windows platform On Windows platforms, the user ID used to start the mqsistop command must belong to the Administrators group.

Linux platform UNIX platform On Linux and UNIX systems, the user ID used to invoke the mqsistop 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 be the same as the user ID that started the component.
  • If you specify the -q parameter, the user ID must be a member of the mqm group.
The security requirements for using the mqsistop command are summarized in the following topics:

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 platform Windows
To stop the Database Instance manager:
mqsistop DatabaseInstanceMgr
Windows platform Linux platform UNIX platform Windows, Linux, and UNIX systems
To stop the broker, mybroker, and the WebSphere MQ queue manager associated with it:
mqsistop mybroker -q
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:34:07

an28080_ This topic's URL is: