[Info-vax] New filesystem mentioned

[Dave Froble]

On 5/16/2019 10:04 AM, Bob Koehler wrote:
> In article <qbih1l$t93$1 at dont-email.me>, Dave Froble <davef at tsoft-inc.com> writes:
>>
>> "Has to" ??
>>
>> Well, only if locking is required.
>
>     Since we're talking cluster support, locking is required.

Hmmm,  I think the topic was filesystems ....

Yes, I'm pretty sure, filesystems, and what could be used in a cluster, 
among other things.

Of course, if some arbitrary filesystem would be used in a VMS cluster, 
in addition to needing to be compatible with VMS, or VMS be compatible 
with the file system, some form of locking would be required, and since 
the DLM is already a "black box" tool on VMS, why not use it?

>> Regardless, using a tool such as DLM does not imply that the tool (DLM)
>> is part of the XQP, filesystem, etc.
>
>     No, DLM is a separate part of the kernel, which is used by and
>     required by the XQP and such.

Damn, that brings up another question.  Is the DLM part of the kernel? 
I don't know the details of the implementation, but, I'd at least hope 
it is not.  That would allow it to be used in any modular type of OS. 
And before anyone mentions parts of the kernel might use the DLM, I'd 
guess that might happen.  Doesn't mean anything used by the kernel is 
part of the kernel.

Isn't that sort of keeping to the concepts of OO?

>> Since there is a likelyhood of there being a MOVL somewhere in the code,
>> should that imply that Macro-32 is part of whatever is using it?
>
>     No, but it is almost certainly required by the code when running on
>     a VAX.
>

As the DLM, or something that does the same job, is required for file 
access coordination.

-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486