Experimental Physics and
Industrial Control System

Hi Emmanuel,

For most of the databases I use, there is a corresponding autosave-request file, written by the author of the database.  I think the author is probably the entity best placed to determine which PVs need to be autosaved so that the database can reinitialize itself to the state it was in before the ioc reboot.  I would not trust dbgrep to choose autosave PVs.

Normally, I just include a line of the form
    file <request file> <macro definitions>
for each database whose PVs I want autosaved.

With this practice, an ioc configuration doesn't have to specify PVs at all, so doesn't have to react to PV-name changes.

By the way, there is code in synApps (makeAutosaveFiles.py) that will go through all of the .cmd and .substitution files in an ioc directory, find corresponding request files, if they exist, and write a request file for the ioc.  This software relies on a naming convention: for each mydatabase.db there is a mydatabase_settings.req.

Tim

---

From: "Emmanuel Mayssat" <[email protected]>
To: [email protected]
Sent: Friday, June 7, 2013 12:30:40 PM
Subject: PV name change and autosave

To be compliant with a naming convention, changing the name of a PV should be a "trivial" operation.

That is true particularly for PV that are not used in higher level software (seq, feedback, info chart, etc)

Let's focus just for a moment on autosave.

Can the req file, generate itself "automatically"?

dbgrep *O > myfile.req

could do the trick, if you naming convention appends "O" at the end of the output records.

Unfortunately redirection on dbgrep doesn't work since 3.14.10...

Do redirection on dbgrep work in 3.14.12.3+ ?

Of course the req file can be generated manually starting with dbl * > dblist.raw

How do you generate you req file after a simple PV name change?

--

Emmanuel