🚀 go-pugleaf

In article <1993Jan12.153551.15221@kpc.com>, wheeler@thorn.kpc.com (Lloyd
Wheeler) writes:

|>In article <1993Jan7.195359.1@vax.path.ox.ac.uk>, jasper@vax.path.ox.ac.uk
|>writes:
|>|> In article <4362@mitech.com>, gjc@mitech.com (George J. Carrette) writes:
|>|> > How are people managing their sources now that there are two VMS
|>|> > platforms, VAX and ALPHA?
|>|> > 
|>|> > For example, I would love to be able to access my CMS libraries
|>|> > that are sitting on my VAX directly from my ALPHA machines.
|>|> > However, CMS does not support any network operations, and mixed vms
|>|> > clusters are not something that claim to be supported.
|>|> > 
|>|> o o o
|>|>
|>|> Other options are said to be DFS and DQS. Any comments?
|>
|>DQS (Distributed Queueing Services) would not, per se, provide a shared
|>filesystem, but simply a method for submitting jobs cross-network.
|>
|>DFS (Distributed File System) provides a shared filesystem approach, but at
|>least as of a couple years ago (circa 1990-1991) it did not support shared
|>access to modifiable files (that is, it didn't support record locking).  In
|>the same timeframe, such a modifiable file was at the heart of a CMS library,
|>and hence using DFS would restrict you to a single CMS library access at a
|>time (if memory serves).
|>
|>Things may have changed in either CMS or DFS;  I suggest that you just get 
|>a very clear answer before you buy (although I don't recall a reference to 
|>CMS, the limitations on filesharing were outlined pretty clearly in the DFS 
|>documentation).

My understanding of the CMS docs is that DFS is what you are intended to use for
sharing CMS in that manner. Don't know how though...

Certainly the VMSy bits must have been pruned to get it running on the ULTIX
boxen.

--

Phill Hallam-Baker