Re: [foxboro] AW: AW: format in Alarm Manager

Re:  Why do these messages go to the AM (which should only show alarms) =
at
all if they are no alarms?

They only go to the AM display if they are sent there. There is no
requirement that they be sent to the AM.


The SENDMSG and SENDCONF statements specify an alarm message group with =
TO
MSGGRx.


You control whether or not they go to the AM by controlling what is in =
the
Message Group.


I assume that this behavior was desired at some point. Perhaps you =
should
change your configuration.



Re: On the other hand, if they have to go to the AM then why not make =
them
"operable" (e.g. some sort of quittable) by the AM? =20

Originally, sequence messages were sent to an application called the
Operator Message Interface (OMI). This was replaced by ODS (sold in
conjunction with RBatch)  later. I'm not sure of the availability of =
either
application today.

Of course, the messages can be recorded in any of the historians. =
Moreover,
applications like FoxPage and cpShell can be used with these messages =
to
accomplish mighty tasks.



In short, while the implementation of Sequence Messages may not match =
your
usage, they are not useless when applied properly.


Hope this helps.

Alex Johnson
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx
For the latest information on ArchestrA, go to
www.invensys.com/Archestra.html.

 -----Original Message-----
From:   Sascha Wildner [mailto:swildner@xxxxxxxxxx]=20
Sent:   Wednesday, February 19, 2003 10:08 AM
To:     foxboro@xxxxxxxxxxxxx
Subject:        [foxboro] AW: AW: format in Alarm Manager


> -----Urspr=FCngliche Nachricht-----
> Von: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]Im Auftrag von Johnson, Alex
> (Foxboro)
> Gesendet: Dienstag, 18. Februar 2003 20:34
> An: foxboro@xxxxxxxxxxxxx
> Betreff: Re: [foxboro] AW: format in Alarm Manager
>
> The reason for this is that they are not alarms. Notice that the
> .UNACK parameter of the Sequence Block is not set when these
> messages are issued.
>
> In fact, if you examine the message displayed on the screen it
> is an "INFO" message not an alarm.

While this is satisfying as an answer, as a concept it is not.  Why do
these messages go to the AM (which should only show alarms) at all if =
they
are no alarms?  On the other hand, if they have to go to the AM then =
why
not make them "operable" (e.g. some sort of quittable) by the AM?  In =
real
life you always need assistance from someone with the appropriate
privileges to make them go away since you don't want to allow the =
operators
to clear alarms.

Regards,
Sascha

=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: