Re: Access Security Config File (ACF) size?

[Érico Nogueira Rolim via Tech-talk <tech-talk at aps.anl.gov>]

I don't change the ASG during operation. I use rePutField to set ASG
conditionally based on record name, only at startup.


https://urldefense.us/v3/__https://github.com/lnls-dig/afc-epics-ioc/blob/master/iocBoot/iocutca/apply_asg.cmd__;!!G_uCfscf7eWS!aYf-GIZO5qeUPRLZ3bzPrQzz-9Hmm5AfztV4xYB8OhBon4QE6KUWAqUMxvRDc724-GI-QHRZk9UwoZANPzYzUjrOEI4$ 


In other cases, ASG is fixed and CALC expressions are used to determine
the rules.


Even so, when you bring up an IOC, you need to define which ASG its
records will use. Is that fixed for the kind of IOC, or could you bring
up two IOCs for the same kind of device with different ASGs used for
their records?


What is your mechanism for this? Do all relevant records have
field(ASG,"...")? Do they have field(ASG,"$(ASG)"), possibly with a
default value?


I'm using retools because the ASG assignment is relatively simple and I
found it interesting to avoid cluttering up the template files.


Cheers,

Érico

On 4/23/26 06:22, Ralph Lange via Tech-talk wrote:
> Interesting.
> I would never consider changing the ASG of a record...
> I am with team Andrew on this: Keep the ASG fixed and use the
> CALC-like expressions engine inside Access Security to dynamically
> change the rules (behavior) of the group instead of changing the
> records that it applies to. The CALC-mechanism is less invasive, very
> flexible and uses monitors, so changes are applied automatically as
> the controlling PV changes value.
>
> Cheers,
> ~Ralph



Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente.

Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately.