Experimental Physics and
Industrial Control System

"Allison, Stephanie" <[email protected]> · Thu, 23 Apr 2015 17:04:21 +0000

Hi Ralph,

I still use the old dbreport that comes with ye olde gdct for getting a nice sorted one-line list of records:
http://www.slac.stanford.edu/grp/ssrl/spear/epics/extensions/dbreport/dbreport.txt

But dbreport needs maintenance.   I'm sure there are better tools.  

For checking out a dbd and db file, I run dbReadTest (see 6.23 of 3.14.12 app dev guide) on resultant .db files after running make on the Db area of my app.  dbReadTest finds a multitude of sins and saves me multiple restarts of an IOC due to oops's.

Stephanie

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf
> Of Ralph Lange
> Sent: Thursday, April 23, 2015 2:56 AM
> To: EPICS Tech-Talk
> Subject: DBD/DB validator?
> 
> Dear all,
> 
> Ages ago I remember there was a tool called 'dbst' that could be used to
> validate DBD/DB setups and that could dump DBs in a sorted, normalized
> way (only non-default value fields, standard indentation) to make them
> easily comparable with diff and such.
> 
> Is dbst still around? I suppose there are more recent ways nowadays.
> Perl/Python? Web-Service?
> (I do like the idea of using the same library as the IOC, though...)
> 
> What is a good way to do database validation?
> 
> Thanks a lot,
> ~Ralph

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System