Database Locking Inquiry


System Maintenance Menu -> Database Locking Inquiry

In a multi-user network environment, the different operators using the software need to be able to share the data files.
When a user is updating a record in a data file, other users may view that file, inquire and generate reports from that file, but they may not make changes to that same record in the file, at the same time.
The software has to be able to identify and save any changes, before another user can update the same record.

If a user attempts to write to a record being updated by another user, a warning is displayed at the bottom of the screen:

WAITING FOR DATABASE RESPONSE - FILE: RSKF
or
RECORD LOCKED - WAITING - FILE: ARCF
Example:

ARCF (Customer File) in this example is the filename being locked, preventing a Customer Payment from being accepted, because another session had the same customer record open.
It is important to note this file name (ARCF) displayed in the error lock message at the bottom of the screen.

Use this Database Locking Inquiry utility to identify the operators currently locking a specific Oracle, MSSQL, or Pro-Isam file.
Then approach the identified users to request that they complete activity and free up the locked data file. When the record is released, the warning message will disappear from the screen and your program will continue.

Note: To prevent unnecessary file locking, it is recommended that users always exit to the menu screen when a task is completed, and do NOT leave any screen sitting in program option unnecessarily.

The prompts in this record locking inquiry are:

FILE LOCK BASE ON
Select one of the Database or Terminal locking situations and proceed as follows:

ACTIONS:
Additional actions provided by buttons on the Database Locking Inquiry screen include:


Topic Keyword: FINDLOCK
Converted from CHM to HTML with chm2web Pro 2.85 (unicode)