dcmstart (Start multinode area or subarea)

The dcmstart command starts the following OpenTP1 nodes normally at the same time or restarts them at the same time:

All OpenTP1 nodes that configure multinode areas to which the OpenTP1 node corresponding to the command input environment variable DCDIR belongs
All OpenTP1 nodes that configure the specified multinode subareas
OpenTP1 nodes with the specified w option

Processing for an OpenTP1 node differs depending on its status taken when the dcmstart command is executed.

The dcmstart command watches all OpenTP1 nodes in the specified range until it verifies that they have been successfully started up or failed to start up. The command reports (by issuing a message) OpenTP1 nodes under startup process every about 30 seconds.

If the command cannot verify success in, or failure to, start up before a certain time (the value specified in dcmstart_watch_time of the multinode configuration definition) from entry of the command, the system outputs a message and discontinues watching the remaining nodes. Startup process continues for these nodes, but some may be delayed in starting. The user must check the pending nodes and take appropriate actions.

You cannot verify the startup of an OpenTP1 node using the dcmstart command in the following case:

Although a start instruction was issued to the OpenTP1 node, the status of the OpenTP1 node did not change from "stopped" (TERM) during the start verify time.
Typical cases are as follows:
1. Although the OpenTP1 node received a start instruction, initialization takes too much time and the status of OpenTP1 does not change to "started".
2. For some reason, the OpenTP1 node start command cannot be activated in the OpenTP1 node that you request to start.

For an OpenTP1 node using the system switchover facility, startup process takes place for its running and standby systems. When issued, a message relates to both systems.

-n

Forces to start each OpenTP1 node normally independently of the previous termination mode. If this option is not specified, the startup mode is determined on the basis of the previous termination mode.

Previous termination mode was normal termination => normal startup

Previous termination mode was other than normal termination => restart

-p

The command returns the moment it requests an OpenTP1 node to start. The result of startup processing for the node is not checked.

-t start-verify-time~((0-65535))

Specify the length of time to verify the startup of an OpenTP1 node in seconds.

Since a start verification is performed every 5 seconds, you may need to wait longer than the specified time. If you do not specify this option, 20 is assumed. If you specify a value between 1 and 19, 20 is also assumed. When you specify 0, the system continues monitoring the node until it confirms that the OpenTP1 node is completely started.

If the value specified for this option is smaller than the value specified in the dcmstart_watch_time operand in the multinode configuration definition, the value specified in the dcmstart_watch_time operand takes precedence.

-g multinode-subarea-identifier~<1-8 character identifier>

Specifies one identifier for the multinode subarea to start. If an asterisk (*) is specified as the subarea name, it is assumed that a multinode area has been specified. Use \ or " instead of * so that the name is not extended to a shell. The -g option enables normal startup or restart of all OpenTP1 nodes configuring multinode areas or subareas specified in the definition command dcmarea of the multinode configuration definition.

-w node-identifier~<4 character identifier>

Starts the specified OpenTP1 node. When more than one node identifier is specified, a comma (,) must be placed between identifiers.

Message ID	Description	Output destination
KFCA01860-E	dcmstart command input format is invalid.	Standard error output
KFCA04603-I	OpenTP1 node began the startup processing.	Standard output
KFCA04604-I	OpenTP1 node became online.	Standard output
KFCA04605-W	OpenTP1 node has not been activated.	Standard output
KFCA04606-W	Startup of OpenTP1 node could not be confirmed.	Standard output
KFCA04613-E	The dcmstart command argument is invalid.	Standard error output
KFCA04615-E	Error exists in the definition file.	Standard error output
KFCA04616-E	Error exists in the multinode configuration definition.	Standard error output
KFCA04617-E	Command specification does not match the specification in the multinode configuration definition.	Standard error output
KFCA04619-W	OpenTP1 node exceeded its startup watch time.	Standard output
KFCA04620-I	OpenTP1 node is being activated.	Standard output
KFCA04621-E	Error occurred during executing the multinode function.	Standard error output
KFCA04625-I	OpenTP1 node is now in standby mode.	Standard output

In the process of starting each OpenTP1 node with the dcmstart command, inquiry-response messages are suppressed.
Each OpenTP1 node can be started independently with the dcstart command. The dcmstart and dcstart commands must not be executed concurrently. Executing these two concurrently may cause the dcmstart command's message to become invalid.
If a response from the OpenTP1 node to which a startup instruction is sent does not come within the maximum wait time specified in the multinode configuration definition, a message indicating the occurrence of timeout is output and the processing for the OpenTP1 node discontinues.
System operation is not guaranteed when the dcmstart command is executed at occurrence of system switchover.
The dcmstart command must not be executed concurrently for the same OpenTP1 nodes. Otherwise, the dcmstart command's message may become invalid.
With one OpenTP1 node duplicated in more than one multinode subarea, startup process is valid even if any multinode subarea identifier is specified in the -g option.
For a node for which no host name can be obtained from the multinode physical definition, '********' is placed in the host name area of a message.