WebSphere Message Brokers
File: an28060_
Writer: Bill Oppenheimer

Reference topic

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

mqsistart command - Windows, Linux and UNIX systems

Purpose

Use mqsistart to start a WebSphere Message 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, that are detected by the component, 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 Creating a Configuration Manager on Windows. (If you lock your workstation, the queue manager does not stop).

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.

Responses

  • 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

mqsistart WBRK_BROKER
mqsistart DatabaseInstanceMgr
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:06

an28060_ This topic's URL is: