EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Epics research - RDBMS support for Epics
From: Steven Hunt <[email protected]>
To: [email protected]
Date: Wed, 23 Feb 2005 11:54:35 +0100
As many of you will know - I have been skeptical of the usefulness 
of using an RDBMS for managing and generating epics configuration 
files. I do think however the APS scheme of using Oracle to report 
on the actual status of iocs and client configurations is excellent!  

However one way to look at the problems of the present efforts to use a
RDBMS, is as an interesting challenge! So I would like to ask any of you
who have or are planing to use an RDBMS - to send me a short list of
your list of requirements for such a system. I would prefer a list of
what you think such a system should do, rather than how it should be
done, or what your actual system does.

As a starting point here are some ideas:

1. Be able to quickly and easily load or modify the relational 
database from new or modified template, substitution, or client 
(archiver, alarmhandler, edm, ...) configuration files.
                             
2. To enable non Epics specialists to quickly and easily modify 
the default field values for an Epics database, or client 
configurations. Optionaly also change the on-line value.

3. Be able to quickly and easily generate Epics template, 
substitution, startup, and client config files from the relational 
database.

4. Be able to roll back to any given version of a system, ioc, or 
device, based on date/time  or an alphanumeric 'tag'.

5. To be quick and easy to install and maintain.

As this topic has has a high risk of spontaneous combustion (email flame
wars) I would ask you send your responses directly to me and I will pull
them together. I could start a new email list if there is interest.





Replies:
Re: Epics research - RDBMS support for Epics Trivan Pal

Navigate by Date:
Prev: Re: result of date command on IOC of EVG Korhonen Timo
Next: Re: Epics research - RDBMS support for Epics Trivan Pal
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Building EPICS base Noboru Yamamoto
Next: Re: Epics research - RDBMS support for Epics Trivan Pal
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  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 ·