Possible Bug in 3.14.9 Access Security on mv2100

[Ralph Lange <Ralph.Lange@bessy.de>]

Hello everyone -

trying to switch over the first set of production IOCs to 3.14.9 we are 
seeing a perfectly strange behaviour of Access Security on mv2100 
(ppc603) IOCs:

Environment: 3.14.9 (architecture vxWorks-ppc603), exampleApp from base, 
Tornado 2.0.2 (SNS cross compiler), Linux host.

Having sucessfully loaded a minimal access security file
 ASG(DEFAULT) {
   RULE(1,WRITE)
 }

the mv2100 IOC does not always grant permissions to CA clients for all 
its channels.
Calling asDump() on the IOC prints the correct database (as expected).
The caget, caput, cainfo clients report no read and no write access.
On the other hand, the camonitor clients works. (!!!)
This strange behaviour does not change by introducing HAGs and UAGs that 
should explicitly allow access for the test client.

If asSetFilename() is commented out, Access security is not started 
(asDump() yields nothing), all CA clients get read and write access, 
everything works.

When doing the same tests against a Linux soft IOC, everything works as 
expected.

Under 3.14.8.2 in the same setup, everything works as expected on all 
platforms. This behaviour seems new for 3.14.9.

Does anyone have similar experiences?
Is anyone sucessfully using Access Security in a similar environment?
Any idea how to proceed? (We use CA Put Logging, so we have to have 
Access Security running on the IOCs.)

Clueless,
Ralph