mqsistart command - z/OS®

Use the startcomponent command to start a WebSphere® Message Broker component when its controller (control process) is already running, and the start (/S) command to bring a component into a state in which you can run the appropriate change command.

Purpose

The following table distinguishes between the start (/S) and startcomponent commands, and lists the available options:
Component Command Description
Broker
  • /S <Broker started task name>
  • /F <Broker started task name>,SC
  • Start broker.
  • Starts the broker from a 'stop component' state.
Configuration Manager
  • /S <Configuration Manager started task name>
  • /F <Configuration Manager started task name>,SC
  • Start Configuration Manager.
  • Starts the Configuration Manager from a 'stop component' state.
User Name Server
  • /S <User Name Server started task name>
  • /F <User Name Server started task name>,SC
  • Start User Name Server.
  • Starts the User Name Server from a 'stop component' state.

When the controller address space is started, this causes the component to start automatically. You can change this behavior by using an optional start parameter in the started task. If you set the parameter 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. Two scenarios apply when you use this command:

  1. The controller is started with the parameter MAN instead of AUTO.
  2. After a stopcomponent command, the component has to be restarted.

Syntax

z/OS console command - startcomponent

Synonym: sc

Examples

 F MQ00BRK,sc
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:22:41

an28070_