Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!purdue!decwrl!ucbvax!GRIN1.BITNET!MCGUIRE
From: MCGUIRE@GRIN1.BITNET ("The Sysco Kid ", McGuire,Ed)
Newsgroups: comp.os.vms
Subject: Re: Structure/Login.Com question
Message-ID: <8806212040.AA09331@ucbvax.Berkeley.EDU>
Date: 15 Jun 88 14:58:45 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 32

--------------------------- Begin Forwarded Message --------------------------
Date: Wed, 15 Jun 88 9:43:04 cdt
From: "The Sysco Kid (McGuire,Ed)" 
To:   mwalters@uwyo.bitnet
cc:   "McGuire,Ed" 
Subject: Re: Structure/Login.Com question

Michael,

I'll suggest one solution and you can apply the technique in other creative
ways as you think of them.

Let us imagine that your VMS file directories are organized parallel to your
corporate structure.  I'll illustrate with an example.  There is a directory
for the entire accounting division called [ACCOUNTING], a subdirectory for the
audit department called [ACCOUNTING.AUDIT], and a subdirectory for auditor Jane
Doe called [ACCOUNTING.AUDIT.JANE].

When Jane logs in, her default directory is [ACCOUNTING.AUDIT.JANE].  Now the
DCL command @[--]LOGIN will run the LOGIN.COM in [ACCOUNTING] and the command
@[-]LOGIN will run the one in [ACCOUNTING.AUDIT].  Put those lines in your
SYS$MANAGER:SYLOGIN.COM.  (Jane's personal LOGIN.COM in [ACCOUNTING.AUDIT.JANE]
is run after SYLOGIN by the login program.)

The same commands will also set Mira Doe's account up correctly even though she
is in [DEVELOPMENT.WIDGETS.MIRA].  That is, the [DEVELOPMENT]LOGIN will run,
then the [DEVELOPMENT.WIDGETS]LOGIN will run, and then her personal LOGIN.

Do you see what I mean?

Ed
---------------------------- End Forwarded Message ---------------------------