Run-Time Locking; Removing Locks That Remain After Interrupted Operation - Keithley 4200-SCS Reference Manual

Model 4200-SCS Reference Manual
An example of this lock file, which stores information textually, contains the following:
PID:162
USER:kiadmin
HOST:S4200-P3
TIME:Friday, 03/17/2000, 17:28:40
LIB:
MOD:
FILE:
NOTE

Run-time locking

It is possible to edit, save, and compile any user module in the user library while one of its user
modules is being run. However, run-time user-library locking prevents building of a KULT user
library while one of its user modules is being run in KITE. If you try, you see the message shown in
Figure
Figure 8-51
Run-time lock message
Run-time lock files are generated in the following directory:
%KI_KULT_PATH%\lock
When KITE executes a UTM, a run-time lock file is automatically created during the normal loading
of the user module. The run-time lock file is automatically deleted at the end of the run during
normal unloading of the user module.

Removing locks that remain after interrupted operation

If normal operation of KULT or normal execution of user libraries is interrupted, the protective locks
may not be removed automatically. However, you can remove locks manually via the
kultcleanlocks command-line utility. This utility deletes all lock files located in both of the
following directories:
Execute the kultcleanlocks utility as follows:
1.
2.
3.
4200-901-01 Rev. S / May 2017
my_2nd_lib
VSweep.c
C:\S4200\kiuser\usrlib\my_2nd_lib\lock\my_2nd_lib_VSweep.lck
KULT automatically deletes an edit lock file when the corresponding user module is
closed.
8-51.
• The %KI_KULT_PATH%\lock directory
• The %KI_KULT_PATH%\<library name>\lock directories
Click on the Command Prompt icon on the desktop or in the Start
Command Prompt window opens.
At the Command Prompt, type kultcleanlocks.
Press ENTER. The kultcleanlocks utility executes and deletes all residual lock files.
Return to Section Topics
Section 8: Keithley User Library Tool (KULT)
>
Programs menu. The
8-57