Did this article resolve your question/issue?



Why does the _Lock table have records where _Lock-Usr = ?


TitleWhy does the _Lock table have records where _Lock-Usr = ?
URL Name000044741
Article Number000166343
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: 10.x, 11.1, 11.2, 11.3
OS: All supported platforms
Question/Problem Description
Why does the _Lock table have records where _Lock-Usr = ?
What does it mean if  _Lock._Lock-Usr = ?
If the value of _Lock.Lock-Usr is undefined, why it not necessary to process any further records?
Steps to Reproduce
Clarifying Information
Virtual system tables (VSTs), including the _Lock table, are in-memory data structures with the "structure" or representation of a database table. They are not real database tables or temp-tables.

Several Progress articles on the subject of the _Lock table contain sample code that leaves a "FOR EACH _Lock" block when "_Lock._Lock-Usr = ?".
Error Message
Defect Number
Enhancement Number
The _Lock table has a number of "records" equal to -L, whether those locks are used or not. The internal DB structure which represents the _Lock table is allocated all at once, like an array.
_Lock._Lock-Usr = ? means the lock "record" is currently not in use. Several other fields are set to ? as well (e. g. _Lock-Recid).

Unused locks will all always be at the end of the table - there will not be a used "record" after the first one that reports unknowns.
Last Modified Date11/20/2020 7:30 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.