Well, I forgot to specify it needs to work with 'macros' or rather IN template files
In other words, I want to use template files to overwrite other template files.
Something like
dbLoadTemplate('default_configuration')
dbLoadTemplate('patch_default_configuration')
or
dbLoadRecords(default_conf,macros)
dbLoadRecords(patch_conf,macros)
i.e. I do this for a lot of PVs and fields for each PV at once.
In some case, it is possible to use dbpfs (using epicsEnvSet and an postInit include of a file containing a series of dbpfs ), but it isn't as elegant and may turn out to be a management nightmare. Bu I believe there are parameters that cannot be changed after the iocInit. So it is not a universal solution.
My goal is also to have this feature supported and be part of the epics-base.
The feature I am asking for is very close to what the alias directive is doing.
You can create PV aliases through db templates in 2 different ways:
1/
record(ao, "myAO") {
alias( ...) <-- I don't remember the exact syntax. I use 2nd method all the time
}
2/
alias("myAO", "myAlias") <-- no need to know that myAO is an ao record.
FYI,
--
E
> Date: Fri, 6 Jun 2014 11:14:13 -0500
> From:
[email protected]> To:
[email protected]> Subject: Re: EPICS database Feature request
>
>
>
> On 6/6/2014 10:22 AM, Emmanuel Mayssat wrote:
> > changefield("myAO", VAL, 21)
> >
>
> dbpf("myAO.VAL", 21)
>
> --
> ----------------------------------------------------------
> Pete R. Jemian, Ph.D. <
[email protected]>
> Beam line Controls and Data Acquisition, Group Leader
> Advanced Photon Source, Argonne National Laboratory
> Argonne, IL 60439 630 - 252 - 3189
> -----------------------------------------------------------
> Education is the one thing for which people
> are willing to pay yet not receive.
> -----------------------------------------------------------
>
>