Specifies attributes to a single message handler.

 Every message handler job needs a MessageHandler
 object.

 Message Handler (Mh) Jobs in Different Nodes with their MessageHandler Objects

 If any MessageHandler object is not explicitly
 configured to a node it will likewise be created in the
 runtime system. In this case the attributes are
 assigned their default values. If the user does not
 accept these default values, please create a
 MessageHandler object below the node's $Node object,
 name it MessageHandler and assign desired values to the
 attributes.

 In connection with configuring of a $Node object the
 development environment normally configure a
 MessageHandler object as well.

 Not yet implemented.

 If true, current alarm blocking are stored to file
 and recovered after a restart.

 Size of event log.
 Max number of events that can be stored in the event log.

 Specifies the maximum number of events that the node's
 message handler contemporary will contain in its event
 list, i.e. the skyline of the events. When NoOfEvents
 exceeds MaxNoOfEvents the oldest event disappears from
 the list.

 Specifies the maximum number of contemporary alarms to
 any application job. The attribute is used to prevent a
 single job from occupying whole event list of the
 message handler.

 Specifies the maximum number of contemporary system alarms.
 The attribute is used to limit alarm allocation when
 system alarms are not acknowledged.

 Cycle time for detecting alarm conditions for supervision
 objects which detection is handled by the event monitor, that
 is supervision objects that is not in a PlcPgm and not under
 a signal object.

 Cycle time for reading status of supervision object and sending
 alarm messages.

 The number of active alarms counted from time of boot.

 The number of events counted from time of boot.

 Alarms and events emitted by the system.
 An array of supervisory objects that is triggered by various
 system events or errors.