Starts one or more (named) channels. The start is asynchronous, which means that the start is triggered by the command, but the channel(s) cannot be expected to be active by the time the command returns.
The following list describes the formats.
When a channel name is specified, you may add an asterisk character (*) to the end of the channel name to start all channels that begin with the specified name. In the following example, all channels that begin with chan1 will be started.
start chan1*
The switches control how the names are interpreted. The following table lists and describes the switches that are supported by the start command:
|
Switch |
Description |
|---|---|
-protocol |
The names are interpreted as protocol names, such as MSMQ or File. This allows starting of all listeners/channels of a specified protocol. |
-pulse |
Attempt to start a pulsable channel for a single access/poll cycle. Some protocols such as file can be pulsed. Others, such as HTTP, cannot be pulsed. An attempt to start a nonpulsable channel will result in an error. Pulsing can only be used for starting specific, named channels. |
-active |
The start applies to channels marked active. Active channels start when the start all is issued (by default at the initialization of the server). This is the default for the start command. |
-inactive |
The operation applies to inactive channels. Inactive channels do not start when the start all command is issued. This allows channels to be "reserved" outside of normal operation. |
-both |
The operation starts both active and inactive channels. |
-doflow |
Run the channel startup failure process flow if defined for the listener in the event that the channel does not properly start. |
-noflow |
Do not run the channel startup failure process flow if defined for the listener. This is the default. |
The following examples show usage of the start command:
start chan1
start mq -protocol -doflow
start (mq, file) -protocol -doflow