Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!husc6!uwvax!dogie!uwmcsd1!ig!agate!ucbvax!GALLUA.BITNET!CADS_COLE
From: CADS_COLE@GALLUA.BITNET ("Kevin Cole at Gallaudet U. Washington DC")
Newsgroups: comp.os.vms
Subject: RE: Structure/Login.Com question
Message-ID: <8806211607.AA04221@ucbvax.Berkeley.EDU>
Date: 15 Jun 88 13:28:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 50

Date sent:  15-JUN-1988 08:10:32

Michael Joe Walters  writes:

>What I am looking to do (and I am not a technical person) is this. We want
>to have LOGIN.COM files or something similiar that reside in the directory of
>the Division level and each of the department levels. Then when one of the
>users login the LOGIN.COM will be executed on the division level first, the
>department level next, and if it exists, the account level next.
>
>With this kind of setup a division could placed information in the LOGIN.COM
>that is only necessary for that division. This might include messages,
>important information, etc. Everyone in that division would execute the
>LOGIN.COM file when they login. The departments could also do the same thing
>with each person in that department executing the division and then the
>departmental LOGIN.COM.
>
>My question is can this been done without any changes to VMS? Has anyone
>implemented something similar?

Fairly easy I would think...  Set up a directory where all the .COM files are
protected in a way that allows the appropriate parties to read them.  Then (and
this is probably the simplest to implement), just set up LOGIN.COM's at the
account level which execute the appropriate COM files in other areas.

For example, create a directory called [COMMON-DIR].  Create some COM files
like: DIVISION.COM, DEPARTMENT-1.COM, DEPARTMENT-2.COM, etc.  and make sure the
directory and the files have a protection which allows them to be read.

Accounts 1-4 in department one        Accounts 1-4 in department two
have LOGIN.COM's start like:          have LOGIN.COM's start like:

$ @[COMMON-DIR]DIVISION               $ @[COMMON-DIR]DIVISION
$ @[COMMON-DIR]DEPARTMENT-1           $ @[COMMON-DIR]DEPARTMENT-2

(Ultimately, you could get much more complicated and just have one huge master
COM file which has the smarts in it to decide which account called it and
behave in whatever fashion you desire after that, but you said you weren't a
technical person...)

-------------------------------------------------------------------------------
Kevin Cole                    BITNET: KJCOLE@GALLUA.BITNET
Center for Assessment and                               or
Demographic Studies  (CADS)                     CADS_COLE@GALLUA.BITNET
Gallaudet Research Institute  (GRI)     UUCP: ...!psuvax!gallua.bitnet!kjcole
Gallaudet University                    CompuServe: 76167,1406
Washington, D.C.  20002
(202) 651-5575

             "Hey Rocky!  Watch me pull a rabbit out of my hat!"