Coordinating Locking using the Byte-Range Driver (Migration,Performance)
Created at 31 JUL 1996 11:16AM
To coordinate locking between Advanced Revelation 3.1x and OpenInsight
on a byte-range network, both Arev and OI must use the same lock file.
Arev uses the REVBOOT file by default, but the lock file can be set using
the DOS environment variable ARevLockFile.
OpenInsight uses the file specified by REVLockFile in the OENGINE section
of WIN.INI or by REVLockFile in the BYTERANGELOCKING section of OINSIGHT.INI.
To coordinate locking to use the Arev REVBOOT, (and assuming Arev is installed
on the network Q: drive), add these lines to WIN.INI:
[OPENENGINE]
REVLockFile=Q:\AREV\REVBOOT
To coordinate locking to use J:\LOCKFILE, add this line to the AUTOEXEC.BAT
of each station using Arev:
Set ARevLockFile=J:\LOCKFILE
.. and add these lines to the WIN.INI of each station using OpenInsight:
[OPENENGINE]
REVLockFile=J:\LOCKFILE
.. or (alternatively) the OpenEngine locking can be set in the OINSIGHT.INI:
[BYTERANGELOCKING]
REVLockFile=J:\LOCKFILE