Use
Case: Executive, Executive Package: Exec_Shutdown
When maintenance or other changes have to be performed on the ALMA
Observing System it is necessary to shutdown the entire system or
the relevant part of it. This is shown by an Operator who first
orders the shutdown of a particular subsystem and afterwards decides
to close down the entire system.
Goal: Shut down Executive
software.
Contact Author: P. Grosbol
Role(s)/Actor(s):
Primary:
Secondary:
Priority:
Critical
Performance:
On the order of minutes
Frequency of Use:
A few times per month
Preconditions:
- The ALMA software system is running.
- Main operator GUI is available.
Basic
Course:
- The Operator issues a shutdown command from the main operator GUI.
- If observations are being done, the operator is asked to confirm
the shutdown command
- Scheduling is set to manual mode
- Long term scheduling synchronization is terminated.
- Shutdown commands (i.e. cleanUP()) are send to all subsystems and
components in the order defined in the configuration file.
- The states of all components are monitored and displayed on the
operator GUI.
- After all subsystems have been shutdown, all operator clients are
disconnected.
- Error-Monitor and Watchdog-Timer are shutdown.
- All ACS services are terminated
- Alternative Course:
- If some components do not reach the DEFUNCT state within a
defined timeout period, it is attempted to stop them with an
abort command (i.e. aboutToAbort()).
Postconditions:
- ALMA software system has stopped
- Operator GUI is in basic configuration indication subsystem
Issues
to be Determined or Resolved:
- none at this time
Last modified: 31oct03