I agree w/ your concern re the settings matching w/ pvAccessCPP.
I noticed these env variables were missing when I was asked to update our iocAdmin (iocStats)
with the PVA env variables. We use it to create PV's that display how each
env variable is set, but I don't think it will reflect how one env variable can get
it's default from another env variable.
There doesn't appear to be any support in the CA libs either re staying in sync
with the env variables in envDefs.h.
There are 2 copies online of pvAccessConfig.xlsx I know of: /github. com/epics- base/pvDataWWW/ blob/master/ mainPage/ pvAccessConfig. xlsx /www.google. com/url? sa=t&rct= j&q=&esrc= s&source= web&cd= 2&cad=rja& uact=8& ved=2ahUKEwiMqY 7h677eAhWHLnwKH SkmA2sQFjABegQI ABAC&url= http%3A% 2F%2Fepics- pvdata. sourceforge. net%2FpvAccessC onfig.xlsx& usg=AOvVaw0zhw0 cg-Urqyso6CLM_ 0Gf
https:/
https:/
Both appear to be compatible.
I agree w/ your concern re the settings matching w/ pvAccessCPP.
I noticed these env variables were missing when I was asked to update our iocAdmin (iocStats)
with the PVA env variables. We use it to create PV's that display how each
env variable is set, but I don't think it will reflect how one env variable can get
it's default from another env variable.
There doesn't appear to be any support in the CA libs either re staying in sync
with the env variables in envDefs.h.