2.2.6 disconnect

usage: disconnect [ -ecsa ] [ -ec ] [ -local ] [ -q ] [ -verbose] <running server process>

By using this command, it possible to let an EC/ECSA and its workflows run in disconnected mode during Platform upgrade, in order to avoid downtime.

Note!

Since a batch workflow cannot run without contact with the Platform, this command should only be executed on ECs/ECSAs running real-time workflows. If an EC/ECSA running a batch workflow is disconnected, the workflow will abort.

After disconnect, the EC/ECSA will continue executing real-time workflows without interference from the Platform and there will be no risk that new software is downloaded to the EC/ECSA during the Platform upgrade.

After the upgrade has been performed, each EC/ECSA has to be restarted in order to re-connect to the Platform, refer to 2.1.10 restart for more information.

The command accepts the following options:

Option	Description
[-ecsa]	Use this option to disconnect only ECSAs, for example: `MZ>> disconnect -ecsa` If using this option without any ECSA process specified, as in the example, all ECSAs will be disconnected. If a non-ECSA process is specified, fault code 4 will be returned, for example: `MZ>> disconnect -ecsa ec1`
[-ec]	Use this option to disconnect only ECs, for example: `MZ>> disconnect -ec` If using this option without any EC process specified, as in the example, all ECs will be disconnected. If a non-EC process is specified, fault code 4 will be returned, for example: `MZ>> disconnect -ec ecsa1`
[-local]	Use this option to disconnect an EC/ECSA that is running on a local machine, for example: MZ>> disconnect -local ec1 In the example, the local EC process named ec1 will be disconnected. If using this option without any EC/ECSA process specified, all local ECs/ECSAs will be disconnected.
[-q]	Quiet mode. Use this option to eliminate the display of any report during execution.
[-verbose]	Verbose mode. This option will print extended error information.

By running the disconnect command from the Platform without any options, all running ECs/ECSAs, on all connected machines, will be disconnected without the need to login to each machine and disconnect them one by one:

MZ>> disconnect

Hint!

To get the latest status information for all local EC/ECSAs, execute the status command as described in 2.1.13 status.

Return Codes

Listed below are the different return codes for the disconnect command:

1-3: Errors only effecting one or more EC/ECSA.
10-11: Fatal error, no EC/ECSA was disconnected.

Code	Description
0	Will be returned if the command was successful.
1	Will be returned if an EC/ECSA process is not running.
2	Will be returned if an EC/ECSA cannot be reached due to a communication problem.
3	Will be returned if an EC/ECSA does not exist.
10	Will be returned if the Platform cannot be reached due to communication problems.
11	Will be returned in case configuration files in `MZ_HOME/etc` contain errors that prevent the command from running.

Next:

2.2.7 dumpsyslog