Lock File (Magic xpa 2.x)
Magic xpa implements record and table locking at two levels. The first level uses the locking mechanism of the underlying vendor-supplied DBMS. The second, optional, level is Magic xpa’s own locking mechanism. The Magic xpalocking mechanism involves creating a lock file in every directory that contains at least one of its tables (data or system files).
When Magic xpa locks a record, it uses a lock file to keep track of that lock. The name of the lock file is specified in this setting. Do not use path names for the Lock file parameter, because the path names are supplied automatically.
The path of the lock file is not specified here. The lock file will be located in the directory of the file being locked. That location can be specified in the Location column of the Database repository, or in the Data Source Name column in the Data repository.
The first user accessing a shared table in a directory causes the directory’s Magic xpa lock file to be opened. Exiting from Magic xpa deletes the Magic xpa lock file.
If the lock file is placed on a network drive (for example, to be used with several servers), then the location should be the server address and not the UNC name. For example: \\143.132.311.11\uplock.dat.
Default: mglock.dat
Change effective: Next session
Magic.ini and Command Line name: LockFile
Magic xpa Locking
Lock Path
Locking Methods
How Do I Determine the Location of the Magic xpa Locking File?
