Channel access security

[frl@aps.anl.gov (Frank Lenkszus)]

I've come across a situation in which I have 20 iocs, each of which will have
a unique access security group with access conditioned on a local process 
variable. The form of the 20 access security rules is the same. I have 2 choices
for handling this. Create 20 unique files each with a single access group, or
create 1 file that includes all 20 access groups. The first option's 
disadvantage is it requires 20 files. The second's disadvantage is that each
ioc will create a channel access connection to the 19 pv's that are not local 
even though the rules invoking those pvs are never used in the that ioc.
Not a pleasant thought. In this case, I'd get 19x20 or 380 superfluous channel
access connections. Sooo, for now, I'll just create a template and use subtool
it create 20 access security files.

It would have been real handy though, if asSetFilename supported macro 
substitution. If that were so, I could defer macro substitution to the
start up command files.  Anyway, I suggest that some future incarnation of
asSetFilename support macro substitution.  Comments?


Frank