Send all notifications for an alarm

      description "NtfSubscriptionControl represents a notification 

        subscription of a notification recipient. 

        The scope attribute is used to select managed object instances included 

        in the subscription. The base object instance of the scope is the 

        object instance name-containing the NtfSubscriptionControl instance. 

        The scope attribute is used to select the data nodes included in the 

        subscription. The base object instance of the scope is the object 

        instance name-containing the NtfSubscriptionControl instance. 

        When the scope attribute is absent, all objects below and including 

        the base object are scoped. The notifications related to the selected 

        managed object instances are candidates to be sent to the address 

        specified by the notificationRecipientAddress attribute.

        The notificationTypes attribute and notificationFilter attribute 

        allow MnS consumers to control which candidate notifications are 

        sent to the notificationRecipientAddress.

        the base object are scoped. 

        For most notification types the scope needs to identify a set of 

        managed object instances, such as for alarm notifications. For some 

        notification types one or more attributes, attribute fields or 

        attribute elements may be specified as well, though, such as for 

        attribute value change notifications. Details on this matter are 

        specified together with the definition of the notification type.

        Note that a scope may also include objects that are not created yet, 

        for example, when a complete subtree is scoped, or when all objects 

        with a specifc object class are scoped. Object instances added after 

        creating the subscription are included in the subscription as well 

        if not explicitely exluded.

        The notifications related to the selected data nodes are candidates 

        to be sent to the address specified by the 

        notificationRecipientAddress attribute.

        The notificationTypes attribute and notificationFilter attribute allow 

        MnS consumers to control which candidate notifications are sent to the 

        notificationRecipientAddress.

        If the notificationTypes attribute is present, its value identifies 

        the notification types that are candidates to be sent to the 

        is applied to the set of candidate notifications. The filter is 

        applicable to all parameters of a notification. Only candidate 

        notifications that pass the filter criteria are sent to the 

        notificationRecipientAddress. If the notificationFilter attribute is 

        absent, all candidate notificatios are sent to the 

        notificationRecipientAddress. If the notificationFilter attribute 

        is absent, all candidate notificatios are sent to the 

        notificationRecipientAddress.

        The producer MnS sending the notification may force the sending of 

        a notification to specific subscriptions, overriding the scope or 

        notificationFilter attributes if they would prevent sending it. 

        To receive notifications, a MnS consumer has to create a 

        NtfSubscriptionControl instance on the MnS producer. A MnS consumer 

        can create a subscription for another MnS consumer since it is not 

        the MnS consumer shall delete the corresponding NtfSubscriptionControl 

        instance.

        When a subscription is created and the notification scope inludes 

        the created subscription object and the subscribed notification types 

        include notifications reporting object creation (notifyMOICreation 

        or notifyMOIChanges), the first notification sent related to the 

        new subscription shall report the creation of the 

        NtfSubscriptionControl instance. Likewise, when a subscription is 

        deleted and the notification scope inludes the deleted subscription 

        object and the subscribed notification types include notifications 

        reporting object deletion (notifyMOIDeletion or notifyMOIChanges), 

        the last notification sent related to the subscription shall report 

        the deletion of the NtfSubscriptionControl instance.

        Creation and deletion of NtfSubscriptionControl instances by MnS 

        consumers is optional; when not supported, the NtfSubscriptionControl 

        When a subscription is created and the notification scope inludes the 

        created subscription object and the subscribed notification types 

        include notifications reporting object creation (notifyMOICreation or 

        notifyMOIChanges), the first notification sent related to the new 

        subscription shall report the creation of the NtfSubscriptionControl 

        instance. Likewise, when a subscription is deleted and the notification 

        scope inludes the deleted subscription object and the subscribed 

        notification types include notifications reporting object deletion 

        (notifyMOIDeletion or notifyMOIChanges), the last notification sent 

        related to the subscription shall report the deletion of the 

        NtfSubscriptionControl instance.

        Creation and deletion of NtfSubscriptionControl instances by MnS c

        onsumers is optional; when not supported, the NtfSubscriptionControl 

        instances may be created and deleted by the system or be 

        pre-installed.";