Lock/Mutex to prevent "caget" from cutting in between updating multiple fields

["Zhang, Dehong" <dhzhang@slac.stanford.edu>]

Hi,

In my custom record, I need to update multiple fields atomically so they stay

synchronized -- all updated, or none updated; not a few updated, but a few with the

old data.  If I use my own mutex, I suspect that "caget" can cut in between the

updating and gets, for example, new data with old time stamp, or old data with

new time stamp depending on the order of updating.

And I guess "camonitor" would not have this problem because it would be the server

pushing the whole set (field itself and time stamp for instance).  Is this right?

So to close this hole with "caget", which global lock should I use?  dbScanLock?

Thank you, best regards,

Dehong