isCOBOL Server allows locks on indexed files to be managed internally, without demanding the lock request to the file handler. In order to activate this feature, the following setting must appear in the server configuration:

isCOBOL Server can be either a iscserver process running as Application Server, a iscserver process running as File Server or a iscserver process running as both. In the third case, locks acquired by the Application Server clients are managed together with locks acquired by the File Server clients.

Note - For this feature to work correctly, the configuration property iscobol.as.multitasking must be either omitted or set to 0.

Making isCOBOL Server manage locks itself guarantees that all the lock clauses are supported, regardless of the file handler; this is particularly useful when working on databases via Database Bridge. Active locks can be monitored and managed through the server administration panel:

The only disadvantage is that locks are held only between the clients of the same isCOBOL Server and don’t affect COBOL programs running outside of the isCOBOL Server as well as third party applications.