mqsistop command

Supported platforms

  • Windows
  • Linux and UNIX systems
  • z/OS

Purpose

Use the mqsistop command to stop a WebSphere Event Broker component. On z/OS, the controller must be running.

Start of changeThe following table distinguishes between the stop (/P) and stopcomponent commands, and lists the available options:
  • Use the stop (/P) command to bring a component into a state in which you can run the appropriate change command.
  • Use the stopcomponent command to stop a broker, Configuration Manager, or User Name Server when its controller (control process) is already running.
Component Command Description
Broker
  • /P <brokerName>
  • /F <brokerName>,P
  • /F <brokerName>,PC
  • Stop broker.
  • Stop broker; this is the same as /P. You can also use /F <brokerName>,STOP
  • Stop broker component. This stops the broker process (including any execution group address spaces), but leaves the message broker console command server running inside the controller address space. This allows you to run the mqsichangebroker command console command. Restart the broker afterwards by running the mqsistart command (SC) console command.
Configuration Manager
  • /P <configMgrName>
  • /F <configMgrName>,P
  • /F <configMgrName>,PC
  • Stop Configuration Manager.
  • Stop Configuration Manager; this is the same as /P. You can also use /F <configMgrName>,STOP
  • Stop Configuration Manager component. This stops the Configuration Manager process, but leaves the message broker console command server running inside the controller address space. This allows you to run the mqsichangeconfigmgr command console command. Restart the broker afterwards by running the mqsistart command (SC) console command.
User Name Server
  • /P <User Name ServerName>
  • /F <User Name Server>,P
  • /F <User Name Server>,PC
  • Stop User Name Server.
  • Stop User Name Server; this is the same as /P. You can also use /F <User Name Server>,STOP
  • Stop User Name Server component. This stops the User Name Server process, but leaves the message broker console command server running inside the controller address space. This allows you to run the mqsichangeusernameserver command console command. Restart the broker afterwards by running the mqsistart command (SC) console command.
End of change

Syntax

Windows platforms, Linux, and UNIX systems

z/OS

Synonym: pc

Parameters

component
(Required - Windows, Linux, and UNIX systems) 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 - Windows, Linux, and UNIX systems only) Stop the WebSphere MQ queue manager associated with this WebSphere Event Broker component.

Specify this flag only if the WebSphere Event Broker component is the last (or only) WebSphere 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 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) 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.

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.

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

Windows, Linux, and UNIX systems 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
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
z/OS
To stop a broker called MQ00BRK:
F MQ00BRK,pc