Experimental Physics and
Industrial Control System

"Brown, Garth" <[email protected]> · Thu, 14 Nov 2013 17:09:55 -0800

We have a module which is used by many systems in slightly different environments. Each environment has a long list of default settings that work for nearly every IOC in that environment.
If my environments are SYS0 and SYS1, and I want to define default values for the macro TS1ST, I can do something like this:
Substitutions file for SYS0 contains
file evrPatternAll.db 
{     
  pattern { SYS, SYS0_TS1, SYS1_TS1, TS1ST, ....    }
        { SYS0,         1,        2,      \$(TS1ST=$($(SYS)_TS1)) , ....   }
....

And in the output, $($(SYS)_TS1)) becomes $(SYS0_TS1), which becomes 1, so $(TS1ST) from evrPatternAll.db is substituted by $(TS1ST=1), which is what I wanted as the default value in SYS0.
If I want to use this for SYS1, I could change that to 
file evrPatternAll.db 
{     
  pattern { SYS, SYS0_TS1, SYS1_TS1, TS1ST, ....    }
        { SYS1,         1,        2,      \$(TS1ST=$($(SYS)_TS1)) , ....   }
....

And I get $(TS1ST=2), the desired SYS1 default value. 
That may be a useful trick, but it's not quite what I want. The file my example is based on has lots more in the pattern line, and many more lines. To simplify maintenance and reduce errors for all the installations where we want to take the per-environment defaults, I want a way for users to just define SYS  in one place, preferably a macro in dbLoadRecords. That would let you cut and paste one st.cmd line into new systems, while maintaining per-environment defaults centrally. Does anyone have a way to do that, or good alternatives for this type of problem?

Thanks,
Garth

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System