Browse Prior Art Database

Lock Ownership by a Function Rather than by a User

IP.com Disclosure Number: IPCOM000107902D
Original Publication Date: 1992-Mar-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 1 page(s) / 65K

Publishing Venue

IBM

Related People

Barnes, CC: AUTHOR [+2]

Abstract

Traditionally, locks acquired on an object have been associated with a single user. This method has the characteristic of allowing only this user to manipulate the lock and the object which is locked, or conversely, allows the user to deny or restrict access to the object until the lock is released. Some functions, however, require that ALL users are denied access to the object, including the requestor of the function, until said function completes successfully.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 57% of the total text.

Lock Ownership by a Function Rather than by a User

      Traditionally, locks acquired on an object have been associated
with a single user.  This method has the characteristic of allowing
only this user to manipulate the lock and the object which is locked,
or conversely, allows the user to deny or restrict access to the
object until the lock is released.  Some functions, however, require
that ALL users are denied access to the object, including the
requestor of the function, until said function completes
successfully.

      With this new method of locking, an object is locked by a
function and remains inaccessible to other users/functions until this
specific function completes.  If the function terminates abnormally,
and the system is still available, the lock still inhibits access to
the object.  The function can be restarted by anyone with the
authority to initiate said function.

      With the advent of an administrator function which must
complete before the resource upon which it is acting is available for
use, a new scheme of locking was developed. Since certain
processes/functions are designated to groups of users, locking for a
function was introduced.  The lock was implicitly created at the
outset of the function and was recorded as having the function name
as the owner of the lock as opposed to the userid of the requestor.
This allowed any user with the required authority to monitor and
manipulate the function.  With the creation of a functio...