From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: ***
X-Spam-Status: No, score=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID,
	RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no
	version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f7344,e291a4dd07824524
X-Google-Attributes: gidf7344,public
X-Google-Thread: 103376,e291a4dd07824524
X-Google-Attributes: gid103376,public
From: "Jay and Cathy Peterson" <JPeterson@PCBYTE.net>
Subject: Re: VAX Ada Tasks and VMS Lock Manager
Date: 1997/07/22
Message-ID: <01bc96ee$d38ac0c0$84ecced0@jpeterson>#1/1
X-Deja-AN: 258226820
References: <01bc9579$39aaaf40$83ecced0@jpeterson> <1997Jul21.101731.1@eisner>
 <01bc965a$b5135f60$88ecced0@jpeterson> <1997Jul22.070236.1@eisner>
Organization: (personal)
Newsgroups: comp.lang.ada,comp.os.vms
Date: 1997-07-22T00:00:00+00:00
List-Id: <comp.lang.ada>




Larry Kilgallen <kilgallen@eisner.decus.org> wrote in article
<1997Jul22.070236.1@eisner>...
> In article <01bc965a$b5135f60$88ecced0@jpeterson>, "Jay and Cathy
Peterson" <JPeterson@PCBYTE.net> writes:

[snipped]
> 
> 
> But if you choose to manage your Lock Manager usage such that
> Tasks A, B, C and D each enqueue for their own Lock ID and do
> not share them (as is typical with most designs), the fact that
> subsequent Enqueue calls will not be granted until the exclusive
> holder Lock ID is demoted or dequeued effectively means that
> Tasks B, C, and D will not get the lock until Task A has
> demoted or dequeued its Lock ID.  The affiliation between
> Tasks and Lock IDs, however, is totally under your control.
> 
That answered my question; thank you for taking time to respond :)

Jay Peterson