11.11.1 Setting the System Run Time Locking Setting Off

If a data area flag field called Execution locking on process is set to "Y", a shared lock will be set on the process during execution. If a shared lock on the process cannot be established then execution of the process will fail.

This data area flag is changed on the Work with Execution and Security Settings described in the LANSA for i User Guide.

This means that every time a process is invoked (or a function it contains is invoked) a shared lock is issued against a data area with the same name as the process. Whenever the process (or function) completes execution the shared lock is released.

This locking feature is provided to ensure that you cannot delete or re-compile a process or function while someone else is using it.

Performing this lock and unlock logic takes time and uses computer resource. If desired it can be disabled by setting the run time lock flag to N (for no). However, once disabled, the possibility of deleting an object that someone else is using arises. If this happens, their job will crash.

Note: Compiled processes (not compiled RDML functions) are sensitive to the run time lock flag setting at the time of compilation. If you later change the flag's value you may have to recompile all compiled processes before being able to achieve any performance benefit.

Also see

11.13 Co-ordinate System Settings