Lock Management Architecture
Original Publication Date: 1988-Oct-01
Included in the Prior Art Database: 2005-Feb-15
Described is a process that provides the ability to control which data base activities can occur while selected other data base updates are occurring. It also provides the ability to prohibit selected data base updates from beginning dependent on other activities occurring against the data base. Applications require the ability to lock resources to prevent interference from other processes. These resources may consist of one or more physical records residing on one or more physical databases. For example, the application may require a lock on the resource "invoice", where invoice consists of one header record on one database and multiple invoice details on another database. Operational: The locks are maintained on a database; a table in memory cannot be used since batch and on-line may run concurrently.