The 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 <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. 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.