EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  <19971998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  <19971998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Alarm handler question
From: [email protected] (Janet B. Anderson)
To: [email protected]
Date: Fri, 22 Aug 1997 20:36:23 -0500
I was out of town for a few days so I don't know if anyone already 
answered this question  -

Is there a way to set up the alarm handler to notify people by email
when alarms change?


To set up the alarm handler to send email when an alarm severity changes just
add a $SEVRCOMMAND line to the alh config file for the desired alarm group or
channel. For example, to have email sent to jba when the severity value for
an alarm group named TESTJBAGROUP moves up to MAJOR, include the following line
as part of the TESTJBAGROUP definition.

$SEVRCOMMAND UP_MAJOR echo "Alarm group TESTJBAGROUP" | mailx -s "major alarm" jba



Here is a description of the SEVRCOMMAND and STATCOMMNAD systax.


    $SEVRCOMMAND <severtyChangeValue> <any valid Unix command syntax >
 
       The line starting with $SEVRCOMMAND is optional. It is required only
       when a user wants to start a Unix process when the alarm severity value
       for a group or channel changes. A single group or channel may have
       multiple $SEVRCOMMAND lines. This line defines the change in the
       severity necessary to start the process and defines the process to be
       started. Valid severity change values are -
         UP_INVALID    UP_MAJOR      UP_MINOR         UP_ANY
         DOWN_MAJOR    DOWN_MINOR    DOWN_NO_ALARM    DOWN_ANY

    $STATCOMMAND <alarmStatusStringValue> <any valid Unix command syntax >
 
       The line starting with $STATCOMMAND is optional and valid only for
       an alarm channel. It is required only when a user wants to start a
       Unix process when the alarm status for the channel becomes a specified
       value. A single channel may have multiple $STATCOMMAND lines. This line
       defines the status value necessary to start the process and defines the
       process to be started. Valid alarmStatusString values are defined in the
       alarmString.h header file. Example alarm status string values are -
 
         NO_ALARM   READ      WRITE   HIHI      HIGH   READ_ACCESS
         LOLO       LOW       STATE   COS       COMM   WRITE_ACCESS
         TIMEOUT    HWLIMIT   CALC    SCAN      LINK
         SOFT       BAD_SUB   UDF     DISABLE   SIMM



Janet

Replies:
Re: Alarm handler question Maren Purves

Navigate by Date:
Prev: Booting lots of diskless VxWorks clients Brett M. Kettering
Next: Re: Alarm handler question Maren Purves
Index: 1994  1995  1996  <19971998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Alarm handler question Garrett D. Rinehart
Next: Re: Alarm handler question Maren Purves
Index: 1994  1995  1996  <19971998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·