This locking method causes the lock table (AcuLocks) to be a Vision file instead of an SQL table. This can be accessed via the configuration variable A_MSSQL_VISION_LOCKS_FILE, which must be set to the name of the Vision file that will hold the lock information. Note that you must also set a configuration variable that specifies this file as a Vision file (using a -host variable). This file must be accessible to all users accessing the MS SQL Server, either through a common directory, or through AcuServer.
Also included with the Acu4GL for Microsoft SQL Server product is a small COBOL program that will manage this Vision file ("lockmgr"). This program should be run with the same runtime that you normally use to access MS SQL Server tables, and with the same configuration variables set. The program detects whether Acu4GL for Microsoft SQL Server is available, and detects the A_MSSQL_VISION_LOCKS_FILE variable to determine which file to manage. This program displays all the records in the lockfile, and gives options for removing single records (by highlighting the desired record to remove), or removing all shown records, and also for restricting the shown records by PID, Table, and Database. This program also creates the Vision lock file and is the only method of creating the file. You can refresh the display by selecting the Restrict button, and then pressing OK without restricting the display further.
If everything is working correctly, there should be no records in this table when there are no users accessing MS SQL Server through Acu4GL. The source for this program is in the sample/acu4gl directory.
See also
A_MSSQL_NATIVE_LOCK_TIMEOUT configuration file variable and section B.5.1 "Table Locking" of this appendix.