Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!XEROX.COM!"Bruce_G._Kahler.rochX2" From: "Bruce_G._Kahler.rochX2"@XEROX.COM Newsgroups: comp.os.vms Subject: Re: Login.com question Message-ID: <880622-061340-1351@Xerox> Date: 22 Jun 88 13:12:45 GMT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: bkahl.rochX2@Xerox.COM Organization: The Internet Lines: 13 While mulling over the question about executing separate login.com files for division, department, and individual, I was reminded by the AUTHORIZE manual of an option I'd forgotten (if I ever knew it): the LOGIN command file does not have to be in the user's default directory; it can be anywhere as long as the user has read-access (just put the full file spec in the /LGICMD qualifier in the UAF). This suggests the possibility of a generic top-level login.com that executes the appropriate division, department, and user login.com files by parsing the user's default directory tree, from the lexical function F$DIRECTORY, e.g. By doing it this way instead of , for example, having each user's login.com execute the appropriate division and department procedures, the upper-level ones are protected from users' deciding they want to bypass them, etc. Good Luck.