Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sunybcs!bingvaxu!leah!itsgw!batcomputer!tedcrane
From: tedcrane@batcomputer.UUCP
Newsgroups: comp.os.vms
Subject: Re: RIGHTSLIST database
Message-ID: <2516@batcomputer.tn.cornell.edu>
Date: Tue, 29-Sep-87 18:39:37 EDT
Article-I.D.: batcompu.2516
Posted: Tue Sep 29 18:39:37 1987
Date-Received: Sat, 3-Oct-87 01:18:52 EDT
References: <8709171418.AA07129@mitre-bedford.ARPA>
Reply-To: tedcrane@tcgould.tn.cornell.edu (Ted Crane)
Distribution: world
Organization: Tompkins County Computing, Ithaca, NY
Lines: 39

In article <8709171418.AA07129@mitre-bedford.ARPA> mhg@MITRE-BEDFORD.ARPA (Mark H. Granoff) writes:
>Here's the question: Someone here thought they had seen that a logical
>could be defined to point to the RIGHTSLIST database to make sure that
>the correct one is used.  So, does anyone know where this is documented?
>or what the name of the logical is? and along the same lines, is there
>a logical for SYSUAF.DAT as well?

Yes, you can do that.  RIGHTSLIST, SYSUAF, NETUAF, and all the other .DAT
files in SYS$SYSTEM can be redirected in this fashion.  For that matter,
if you use a little intuition, you will note that VMS and its utilities
are fairly consistent in their rules about looking for files they need.
In the case of AUTHORIZE, LOGINOUT, and the like, they use a open which 
might look like this in FORTRAN:

	open (file='SYSUAF',defaultfile='SYS$SYSTEM:.DAT')

In other words, translate the logical 'SYSUAF'.  If found, use the translation,
if not, use the original string, 'SYSUAF'.  Either way, apply the default
location 'SYS$SYSTEM:.DAT'.

This has extended ramifications.  For example, the image activator uses
a similar mechanism.  Try defining TYPE (the name of an executable)
(for DCL this is frequently the verb, and you can look in SYS$SYSTEM to get
the exceptions) to be something else, or somewhere else.

As to where this is documented, well, it was a while back that I read the
manual, and I can't remember which one.  The bit about the .DAT files is
definitely documented...try the guide to VAXclusters, or look in any manual
for a section describing the initialization/setup of "homogeneous, but not
using a cluster common disk" VAXclusters (i.e., when several nodes in a cluster
share the same user database, but not necessarily the same system images)
(as opposed to a heterogeneous cluster, where they share nothing except a file
system, or a fully homogeneous cluster, where they share everything except
the necessaily unique files, like the paging files).


- ted crane, alias (tc)
tedcrane@tcgould.tn.cornell.edu                       BITNET: tedcrane@CRNLTHRY
{decvax!ucbvax}!tcgould.tn.cornell.edu!tedcrane       DECnet: GOPHER::THC