14.3.12 unlock (unlock)
- Organization of this subsection
(1) Description
This subcommand unlocks a command.
For details, see 14.3.1 Locking between commands.
(2) Rules
-
This subcommand can be executed only when the status of the cluster is one of the following:
-
Cluster available (AVAILABLE)
-
Cluster partially available (PARTIALLY_AVAILABLE)
-
-
The target of this subcommand is the EADS servers whose cluster participation status is online. However, the subcommand cannot be executed in the following cases:
-
An operation is underway.
-
The cluster contains any EADS server whose cluster participation status is standby.
You can determine the cluster participation status with the eztool status command.
-
-
This subcommand can be executed when the target EADS servers are in the following status:
-
Initialized
-
Running
-
Closed
-
(3) Format
eztool unlock
(4) Return code
The following table lists the return codes that this subcommand returns.
No. |
Return code |
Description |
|
---|---|---|---|
eads.command.compat parameter omitted in the command properties |
0300 specified in the eads.command.compat parameter in the command properties |
||
1 |
0 |
0 |
Command execution was successful. |
2 |
101 |
101 |
Initialization of the command failed. |
3 |
110 |
Connection establishment failed. |
|
4 |
111 |
The command failed due to a communication timeout. |
|
5 |
120 |
The command failed due to a syntax error. |
|
6 |
130 |
The command failed because it could not be executed. |
|
7 |
131 |
The command failed because another command was executing. |
|
8 |
150 |
The command failed during execution. |
|
9 |
200 |
The command failed due to a timeout. |
(5) Notes
This subcommand results in an error if all EADS servers are isolated.