| 1994 1995 1996 1997 1998 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 2025 | Index | 1994 1995 1996 1997 1998 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Initial STAT and SEVR for soft ai and ao records |
| From: | Bernhard Kuner <[email protected]> |
| To: | "[email protected]" <[email protected]> |
| Date: | Wed, 02 Feb 2005 08:22:03 +0100 |
And why not setting PINI=Yes to say this record is processed and ready to use and keep the one thing for all records in mind that: a record is undefined and invalid until it is processed! This behaviour is neccessary for all records with hardware access and to start all records this way keeps from beeing puzzled about what state any particular record should be have after the start of an ioc because it is UDF INVALID.
I thought this STAT==UDF alarm stuff was the reason some records were changed to allow their UDF field to be specified at DCT time. But we've also seen a record with UDF==0 specified in the database *still* come up with STAT==UDF. I can't think of a use for this behavior. How about if init_record() were to set STAT/SEVR="NO_ALARM" if it saw that UDF==0?