mqsistart command

Supported platforms

  • Windows
  • Linux and UNIX systems
  • z/OS

Purpose

Windows platforms, Linux, and UNIX systems

Use mqsistart to start a WebSphere Event Broker component. If the queue manager associated with this component (defined in the corresponding create command) is not already running, it is also started by this command. However, no listeners, channels, or channel initiators associated with the started component are started. If you have WebSphere MQ Version 6.0 installed, use the WebSphere MQ Explorer to start any required listeners, channels, or channel initiators. For earlier supported versions of WebSphere MQ, use the WebSphere MQ Services snap-in.

Successful completion of this command indicates that the Windows service, or Linux or UNIX daemon has started successfully, and that the component startup has been initiated. Check the Windows system event log or the Linux or UNIX syslog to determine if the component and all related software have started successfully, are initially active, and remain in an active state. Any errors that have prevented successful startup, detected by the component are recorded in the log. Continue to monitor the Windows system event log or Linux or UNIX syslog.

If the queue manager supporting the component specified on this command is not already running, it is started by this command, but on Windows platforms, is not started as a service. On this system, it stops if you log off. To avoid this happening, either remain logged on, or change the startup status of the queue manager service (described in Creating a Configuration Manager on Windows). (If you lock your workstation, the queue manager does not stop.)

z/OS

Start of changeThe following table distinguishes between the start (/S) and startcomponent commands, and lists the available options:
  • Use the start (/S) command to bring a component into a state in which you can run the appropriate change command.
  • Use the startcomponent command to start a broker, Configuration Manager, or User Name Server when its controller (control process) is already running.
Component Command Description
Broker
  • /S <brokerName>
  • /F <brokerName>,SC
  • Start broker.
  • Starts the broker from a 'stop component' state.
Configuration Manager
  • /S <configMgrName>
  • /F <configMgrName>,SC
  • Start Configuration Manager.
  • Starts the Configuration Manager from a 'stop component' state.
User Name Server
  • /S <User Name ServerName>
  • /F <User Name Server>,SC
  • Start User Name Server.
  • Starts the User Name Server from a 'stop component' state.
End of change

When the controller address space is started, this causes the component to start automatically. This behavior can be changed by an optional start parameter in the started task. If the parameter is set to MAN, the component does not start automatically; the default is AUTO.

Issuing commands against the controller means issuing start, stop, or modify commands from the console to the controller address space. There are two scenarios using this command. The first is that the controller is started with the parameter MAN instead of AUTO. The second is that, after a stopcomponent command, the component has to be restarted.

Syntax

Windows platforms, Linux, and UNIX systems

z/OS

Synonym: sc

Parameters

component
(Required - Windows platforms, and Linux and UNIX systems) This must be a broker name, Configuration Manager name, or one of the fixed values UserNameServer or DatabaseInstanceMgr. All the names are case sensitive on Linux and UNIX systems.

You are strongly recommended to only use this command on Windows platforms if you are using the Derby database.

Authorization

On Windows platforms, the user ID used to invoke this command must have Administrator authority on the local system.

On Linux and UNIX systems, 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 and mqm groups.

When the Windows service, or Linux or UNIX daemon is started, it runs under the user ID specified by the -i flag on the appropriate mqsicreatexxxx command. The component only starts if the ServiceUserID specified is authorized to access the home directory (where WebSphere Event Broker has been installed), and the working directory (if specified by the -w flag on the mqsicreatexxxx command).

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 platforms, Linux, and UNIX systems only:
  • BIP8012 Unable to connect to system components
  • BIP8013 Component does not exist
  • BIP8015 Component cannot be started
  • BIP8018 Component running
  • BIP8024 Unable to locate executable
  • BIP8025 Component disabled
  • BIP8026 Unable to start component
  • BIP8027 Unable to start WebSphere MQ
  • BIP8028 WebSphere MQ unavailable
  • BIP8030 Unable to modify user privileges
  • BIP8048 Unable to start queue manager
  • BIP8056 Unknown queue manager
  • BIP8093 Queue manager being created
  • BIP8094 Queue manager stopping

Examples

Windows platforms, Linux, and UNIX systems:
mqsistart WBRK_BROKER
mqsistart DatabaseInstanceMgr
z/OS
 F MQ00BRK,sc