mqsistop command

Supported platforms

  • Windows 2000, Windows XP
  • UNIX platforms
  • z/OS

Purpose

Use the mqsistop command to stop a WebSphere Business Integration Event Broker component.

On z/OS the controller must be running.

Syntax

Windows platforms and UNIX platforms

z/OS

Synonym: pc

Parameters

component
(Required - Windows platforms and UNIX platforms) This must be either a broker name, or the fixed values:
  • ConfigMgr or UserNameServer on Windows platforms
  • UserNameServer on UNIX platforms
All the names are case sensitive on UNIX platforms
-q
(Optional - Windows platforms and UNIX platforms only) Stop the WebSphere MQ queue manager associated with this resource.

Specify this flag only if the WebSphere Business Integration Event Broker component is the last (or only) WebSphere Business Integration Event 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 Business Integration Event 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 - Windows platforms and UNIX platforms) Immediately stop the broker.

Specify this flag only if invoking the command without it, has failed to stop the broker.

Authorization

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

On UNIX platforms, the user ID used to invoke this command must either be root or must be the same as that specified in the -i parameter when the component was created. It must also be a member of the mqbrkrs group. If you specify the -q parameter to stop the queue manager, the user ID must also 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 UNIX platforms.

Responses

Windows platforms and UNIX platforms only:
  • 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 platforms and UNIX platforms:

mqsistop ConfigMgr -q
z/OS:
F MQ00BRK,pc

Related reference
Syntax preference
mqsistart command