RE: security rules and autosave

["Mooney, Tim M." <mooney@aps.anl.gov>]

More study.  Instead of setting PINI="YES", you could set STAT and SEVR to zero.

Evidently, the reason access-security doesn't get the right value at boot time for PVs used in its calculations,
is that it ignores monitors from PVs if the records hosting them are in alarm.  You can get the record out of
alarm by processing it, or by setting (in the database file) the alarm fields to non-alarm values.

Tim

---

From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of Mooney, Tim M. [mooney@aps.anl.gov]
Sent: Tuesday, July 22, 2014 12:11 PM
To: Touchard Dominique; tech-talk@aps.anl.gov
Subject: RE: security rules and autosave

I get that behavior for any value of a PV used in an access-security rule,
whether it was defined in the database or restored by autosave.  If I
set PINI to get the record processed at init time, it behaves as I think it
should.

record(bo,"$(P)LocalAccess") {
    field(DESC,"AS for Local PCs")
    field(DTYP,"Soft Channel")
    field(ZNAM,"Disabled")
    field(ONAM,"Enabled")
    field(ASG, "controlFields")
    field(PINI, "YES")
    field(UDF, "0")
}

Tim

---

From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of Touchard Dominique [dominique.touchard@ganil.fr]
Sent: Tuesday, July 22, 2014 7:25 AM
To: tech-talk@aps.anl.gov
Subject: security rules and autosave

Hi,

I need some advices on rules and autosave.

I configured a Linux IOC with following rules

================================================================
ASG(FAISCEAU) {

#Operation mode lock
  INPA(DEFAULT:OPState)

#BEAM characteristics lock
  INPB(FAISCEAU:WritePerm)

# We can always read PVs
  RULE(1,READ)

# BEAM Characteristcs could be changed by everyone in maintenance mode and BEAM characteristics unlocked
  RULE(1,WRITE) { CALC("A=0 && B=1") }

# BEAM Characteristcs could be changed only by operators in operation mode and BEAM characteristics unlocked
  RULE(1,WRITE) {
    UAG(operateurs)
    CALC("A=1 && B=1")
  }
}

==============================================================
DEFAULT:OPState could be 0:Maintenance 1:Operation
FAISCEAU:WritePerm could be 0:BEAMLocked 1:BEAMUnlocked

These rules work perfectly when values of DEFAULT:OPState and FAISCEAU:WritePerm are changed  manually.

At starting, with autosave mechanisme, there is a mismatch between right access and  lock values.

Any ideas?

Dominique.