Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 27 OCT 1998 07:08:54PM Henry Bolton wrote:

We have a situation where we would like to lock records in a secondary file whenever the primary record is locked, and unlock them again whenever that primary record is unlocked. The best place to do this, it would seem, is within an MFS that traps LOCK.RECORD, UNLOCK.RECORD, and UNLOCK.ALL calls.

However, these calls are not made to the MFS for a single user system. This results in the primary record being locked internally but the secondary records are not locked at all and can be accessed by other parts of the system. It would seem a better answer would be to trap the RTP Lock and Unlock calls, but this is not possible because I think RTP36 is encoded into the bootstrap and can't be shelled.

Is there any way this task can be achieved without trying to do it at the application level (which would not be easy to implement) ?.

Thanks,

Henry


At 28 OCT 1998 02:51PM Cameron Purdy wrote:

Henry,

As you noted, if the network bit is not set then the file system is not requested to do the lock.

The reason the network bit is not set is because you have an older OENGINE.RUN … even if it has been upgraded to a recent version, it kept the setting of the network bit.

If you info@revelation.com me your engine (ATTN: Cameron) I can verify this and quickly resolve the problem.

Cameron Purdy

Revelation Software

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/cf34f3490fce9fa7852566aa007f287b.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1