EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  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  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: CA Put Logging
From: Matthias Clausen <[email protected]>
To: [email protected]
Cc: Ernest Williams <[email protected]>
Date: Tue, 24 Jun 2008 11:02:11 +0200
Ernest Williams wrote:
Hi,

Has CA Put Logging been integrated into EPICS R3.14.x?
the hook for CA-Put-Logging are available in base for quite some time. The hook for alarm-logging has been added recently.

Is it integrated into iocLog facility?
The hooks are only the mandatory part of this story.
The real workhorse is behind the hooks. (and not part of base)
So the answer is -no- it's not integrated into iocLog.

Behind the alarm-hook is the alarmLogging task which is now in operation at DESY for about a year.
Behind the CA-PutLog hook is the task which Slava Korobov wrote about a decade ago.
As soon as there's time to work on this part we (Bernd) will have a look at the code for put-logging and use the same method as for alarmLogging to forward(push) the putLog messages to the interconnectionServer which finally writes messages into JMS. Besides the fact that we want to send all of the messages: alarms, putLog AND system messages into JMS there's another good reason to work on the putLogmessage task. Namely logging changes when one - or even worse - two or more operators are tuning a record using the slider. The actual implementation only covers the case where lots of changes are applied to the same PV(as a result only one message will be generated when the slider movement finished - here: another PV is accessed, or after a tineout). We want to improve this part of the code. The ring buffer which is already in place for alarmLogging can help us (probably a second instance of it) to keep track of bulk changes on several records in parallel.


If there's interest to work together on this part - let us know.

System logging shall finally also use the JMS message facility. The advantage being that all messages will be stored in one place. All the tools to display and analyze messages can be the same and last and most importantly we can also use the support for redundant connections which is built into the communication between IOC and interconnectionServer.

(btw: there's also a C++ program in operation to replace cmlogMsg and write directly to JMS - on workstations)

-Matthias
References:
CA Put Logging Ernest Williams

Navigate by Date:
Prev: CA Put Logging Ernest Williams
Next: Re: How to specify value to a DBF_ACCESS field Tim Mooney
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: CA Put Logging Ernest Williams
Next: Re: CA Put Logging Ben Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·