14.3.33 isolate (isolates an EADS server)

Organization of this subsection

(1) Description

This subcommand isolates an EADS server.

You can execute this subcommand when the cluster's status is AVAILABLE.
This subcommand can be executed when the EADS server is in the following status:
- Initialized
- Running
- Closed
- Isolated
If this subcommand is executed while the EADS server is running, the subcommand waits until any running user function has terminated, and then isolates the EADS server.

eztool isolate [--stop]

Specify this option to both isolate the EADS server and then terminate it.

If this subcommand is executed on an EADS server that is already isolated, it terminates the EADS server.

The following table lists the return codes that this subcommand returns.

Table 14‒56: Return codes returned by the eztool isolate command
No.	Return code		Description
No.	eads.command.compat parameter omitted in the command properties	0300 specified in the eads.command.compat parameter in the command properties	Description
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.

After the EADS server has been isolated by this subcommand, an EADS server connection error might occur if an API function is executed from an EADS client whose cluster information has not been updated.
If the range becomes disabled and data operations can no longer be continued due to execution of this subcommand, an error results.