IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

mqsistart command - Windows, Linux, and UNIX platforms

Use the mqsistart command to start a broker.

Purpose

If the queue manager associated with this broker (defined by the mqsicreatebroker command) is not already running, it is also started by this command. However, no listeners, channels, or channel initiators associated with the started broker are started. Use WebSphere® MQ Explorer to start any required listeners, channels, or channel initiators.

Successful completion of this command indicates that the Windows service, or Linux or UNIX daemon, has started successfully, and that the broker startup has been initiated. Check the Windows system event log or the Linux or UNIX syslog to determine if the broker and all related software have started successfully, are initially active, and remain in an active state.

All errors that have prevented successful startup, that are detected by the broker, are recorded in the log. Continue to monitor the Windows system event log or Linux or UNIX syslog.

On Windows platforms, the queue manager is not started as a service, and stops if you log off. To avoid this happening, either remain logged on, or change the startup status of the queue manager service as described in Starting a WebSphere MQ queue manager as a Windows service. (If you lock your workstation, the queue manager does not stop).

Syntax

Read syntax diagramSkip visual syntax diagram
>>-mqsistart--broker-------------------------------------------><

Parameters

broker
(Required) Specify the name of the broker that you want to stop.

On Linux and UNIX systems, all names are case sensitive.

Responses

  • BIP8012 Unable to connect to system components
  • BIP8013 Broker does not exist
  • BIP8015 Broker cannot be started
  • BIP8018 Broker running
  • BIP8024 Unable to locate executable
  • BIP8025 Broker disabled
  • BIP8026 Unable to start broker
  • 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
  • BIP8116 Starts a broker

Examples

To start the broker IB9NODE:
mqsistart IB9NODE

an28060_.htm | Last updated Friday, 21 July 2017