Path: utzoo!attcan!uunet!husc6!uwvax!vanvleck!uwmcsd1!ig!agate!ucbvax!INDYVAX.BITNET!IJAH400
From: IJAH400@INDYVAX.BITNET
Newsgroups: comp.os.vms
Subject: Re: Login.com question
Message-ID: <8807031054.AA04509@ucbvax.Berkeley.EDU>
Date: 28 Jun 88 19:07:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 13

< 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
< ...
< 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.

And I was reminded of something I forgot: read-access isn't necessary, you
can execute a command procedure with only execute access to the file...

        - Jim Harvey
        IJAH400@INDYVAX or IJAH400%IVAX.DECNET@GOLD.BACS.INDIANA.EDU