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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: [Fwd: Re: Does DISP work for DB OUT links? Related question] |
From: | Brian Bevins <[email protected]> |
To: | [email protected] |
Date: | Tue, 02 Sep 2003 11:32:09 -0400 |
An additional comments on Jeff's second suggestion:
Fix 2:
There is a new field called AVAL (for asynchronous value) which is initialized at the start of processing to what
is in the VAL field. When processing completes the AVAL field is used to determine if monitors will be sent instead
of VAL.
This does seem like it should be easy to implement.
General Rule: Record support that allows asynchronous processing must do this for any field for which it checks for value change before issuing monitors.
Marty Kraimer
-- Brian S. Bevins, PE Computer Scientist / Mechanical Engineer Thomas Jefferson National Accelerator Facility