BOI Software Entwicklung und Vertrieb GmbH

Phone: +43 (0) 732 / 736423 - 0

Spazgasse 4


4040 Linz, Austria

Informations about ENQ entries (table locks)

Information about ENQ entries
  • ENQ entries are stored in the last record of the TABEX database. They are used in the TABEX standard applications as table locks for tables (for details see below).
  • A maximum of 215 entries can be stored per TABEX database.
  • ENQ entries are intended for a temporary lock and are deleted if the database is reorganized.
  • ENQ entries do not lock automatically but must be requested in the application.
  • For setting, querying and deleting of ENQ entries use the API functions 'BD', 'BE', 'BQ', 'BR', 'BT' and 'BU' (see BOIDOC-211a) or the SSL function 'TABENQ' (see SSL documentation).
  • ENQ entries can be grouped (details in the description of the functions listed above)
  • The TABEX/4 Table Manager automatically sets ENQ entries with default group 'TABVSAM'.
    When using a modification DB, ENQ entries are always stored in the modification DB.
  • TABN02- and TABN05 functions ENQ/DEQ also store ENQ entries with the default group 'TABVSAM', but always in the active database.
  • In TBVW01- and TBVW02 functions ENQ entries are set in the same way as in the TABEX/4 Table manager.
  • No ENQ entries are set when using the TABEX/4 Console.


Changes in ESA data spaces, efficient migration and a new success story: Learn more in our newsletter!


Migration Packages

BOI GmbH offers migration packages for the table management systems SPITAB, TABSYS and VTAS.


» Migration Packages

Success Stories

GDIS and BOI: Carrying on the Success

With TABEX4 JTC, GDIS has introduced the world's fastest Java interface for table access on customer and control data. Learn the details in our new Success Story.


» read this Success Story

» read more Success Stories