Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
<== Date ==> <== Thread ==>

Subject: Re: recDynLink.c for R3.14.1 ?
From: Tim Mooney <mooney@aps.anl.gov>
To: Benjamin Franksen <franksen@mail.bessy.de>
Cc: tech-talk@aps.anl.gov
Date: Thu, 17 Apr 2003 23:05:16 -0500
Benjamin Franksen wrote:

> PS: I finally understood the S_db_Blocked issue (after reading the code
> in base and then re-reading the doc): S_db_Blocked is only returned if
> an existing put notify block in the target record is the *same* object
> (address comparison) as the one that is now being given as argument.
> Multiple putNotifies to the same target record seem to be no problem at
> all as long as they come from different clients, otherwise they are
> ignored. This is make sense, indeed. The Developer's Guide could be a
> little more clear on this point; it says "If a putNotify is already
> active..." which is of course fine if one already knows what is meant.

Uh-oh.  This isn't the way I understood putNotify.  It would be a disaster
for one client to initiate a putNotify trace on the same record, or even a
different record in the same lockset, as an ongoing putNotify trace.  How
could you ensure that the two execution traces would not interfere with
each other?

-- 
Tim Mooney (mooney@aps.anl.gov; 630-252-5417)
Advanced Photon Source
APS Operations Division
Beamline Controls & Data Acquisition Group

References:
RE: recDynLink.c for R3.14.1 ? Feng, Shuchen
Re: recDynLink.c for R3.14.1 ? Tim Mooney
Re: recDynLink.c for R3.14.1 ? Kate Feng
Re: recDynLink.c for R3.14.1 ? Benjamin Franksen
Re: recDynLink.c for R3.14.1 ? Marty Kraimer
Re: recDynLink.c for R3.14.1 ? Benjamin Franksen
Re: recDynLink.c for R3.14.1 ? Marty Kraimer
Re: recDynLink.c for R3.14.1 ? Benjamin Franksen

Navigate by Date:
Prev: CAMAC problems Hammonds, John P.
Next: Re: recDynLink.c for R3.14.1 ? Tim Mooney
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
Navigate by Thread:
Prev: Re: recDynLink.c for R3.14.1 ? Marty Kraimer
Next: Re: recDynLink.c for R3.14.1 ? Tim Mooney
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
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 ·