ACS::MasterComponent Interface Reference

import "mastercomp_if.idl";

Inheritance diagram for ACS::MasterComponent:

[legend]Collaboration diagram for ACS::MasterComponent:

[legend]List of all members.

Public Types
enum	SubsystemStateEvent {   SUBSYSEVENT_INITPASS1, SUBSYSEVENT_INITPASS2, SUBSYSEVENT_REINIT, SUBSYSEVENT_START,   SUBSYSEVENT_STOP, SUBSYSEVENT_SHUTDOWNPASS1, SUBSYSEVENT_SHUTDOWNPASS2, SUBSYSEVENT_ERROR }
Public Member Functions
void	doTransition (in SubsystemStateEvent event) raises (ACSErrTypeCommon::IllegalStateEventEx)

---

Detailed Description

Subsystem Master Component with full access. This interface should be used by the Executive and perhaps other ALMA operations software which is supposed to manipulate the state and modes of subsystems, e.g. during system startup.

---

Member Enumeration Documentation

enum ACS::MasterComponent::SubsystemStateEvent

Enumeration values: SUBSYSEVENT_INITPASS1  SUBSYSEVENT_INITPASS2  SUBSYSEVENT_REINIT  SUBSYSEVENT_START  SUBSYSEVENT_STOP  SUBSYSEVENT_SHUTDOWNPASS1  SUBSYSEVENT_SHUTDOWNPASS2  SUBSYSEVENT_ERROR

---

Member Function Documentation

void ACS::MasterComponent::doTransition (  in SubsystemStateEvent  event  )  raises (ACSErrTypeCommon::IllegalStateEventEx)

Generic method to handle all events. Or should we rather have separate methods for each event? Or both?

---

The documentation for this interface was generated from the following file:

• mastercomp_if.idl

---