Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!utorphys.BITNET!SYSRUTH From: SYSRUTH@utorphys.BITNET Newsgroups: comp.os.vms Subject: RE: Structure/Login.Com question Message-ID: <8806151902.AA09505@gpu.utcs.toronto.edu> Date: 15 Jun 88 17:34:00 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 29 Use the LGICMD flag in the AUTHORIZE utility. This allows you to specify a particular file as the initial login.com for each user. You can do this in either of (at least) two ways: 1. Create a login.com-type file for each division and set the LGICMD flag for each account in each division to the appropriate file. Remember to @sys$login:login.com at the end so the user's own login.com gets run as well. Optionally you could have finer subdivisions within them, each with its own file; however it might be better in this case to have each user execute this file as the first line in his/her own login.com. That way you don't have to have a program which will decide who is in which group. 2. If you have things you want everyone to define, keep using your sylogin.com, and then use some scheme for determining who is in which division (search a file or something?) and @ that division's file. In this case it is not necessary to explicitly call the user's own login.com. Leave the LGICMD flag as just plain LOGIN and both the file you assign to sys$sylogin and sys$login:login.com will be executed. Hope this gives you some ideas. Ruth Milner Systems Manager University of Toronto Physics BITNET: sysruth@utorphys INTERNET: sysruth@aurora.physics.toronto.edu