info-vax@ucbvax.ARPA (03/10/85)
From: ken%hamlet@lbl.arpa Try $ ASSIGN/TABLE=LNM$GROUP_000300 FOO BAR (assigns in group 0300). -Ken Adelman Caltech
info-vax@ucbvax.ARPA (03/11/85)
From: Ronald A. Jarrell <JARRELLRA@VPIVAX3.BITNET>
They speciiiiiiifiy brought that up at the V4 update seminar I took. It's
a planned feature of VMS. THe way DEC suggest you work around it (i think
it's in the release notes, but I'm fairly sure it's also online on the DSIN
system is to run a bunch of detached LOGINOUT processes, give them com files
for input, and give them an arbitray uic in the appropriate group, and give
them GRPNAM.. My workaround, that I never tried, since I don't do that
in my systartup, was to create a new table called GROUP_xxx and put the
logicals their.. The table should then become the right group table
when the users log in.. (or not, don't hold me to this, like I said,
I never botherd to try it...)
-Roninfo-vax@ucbvax.ARPA (08/05/85)
From: boulder!jon@BERKELEY (Jon Corbet)
The previous manager of my VAX decided to get clever some time back,
and set up a bunch of group-dependant logical names so that everybody could
refer to their permanant and scratch disk devices as DP: and DT: respectively.
This was accomplished with a bunch of SET UIC [xxx,1] and ASSIGN/GROUP commands.
Needless to say, this no longer works with VMS v4.1. I have kludged it in the
system login file for now, but it would be nice to be able to assign group
logical names at system startup time again. Has anybody figured out how to
do this? Any help would be much appreciated.
----
Jonathan Corbet
National Center for Atmospheric Research, Field Observing Facility
{seismo|hplabs}!hao!boulder!jon (Thanks to CU CS department)info-vax@ucbvax.ARPA (08/05/85)
From: <#D14@DDATHD21.BITNET> 00000009
Dear Jon,
00000014
you have to start a command procedure as a detached process:
RUN SYS$SYSTEM:LOGOUTIN /INPU=GROUP47.COM /OUTPUT=NL:
/UIC=<47,1> /PROC=GR47
Reinhard Goeth @ Technical University Darmstadt, W.Germany, Europe 00000015
(Beware of the number-sign. It's part of my userid !!!) 00000016
00000017
. 00000018
QUIT 00000019info-vax@ucbvax.ARPA (08/05/85)
From: <#D14@DDATHD21.BITNET>
Dear Jon,
you have to start a command procedure as a detached process:
RUN SYS$SYSTEM:LOGINOUT /INPU=GROUP47.COM /OUTPUT=NL:
/UIC=<47,1> /PROC=GR47
Reinhard Goeth @ Technical University Darmstadt, W.Germany, Europe
(Beware of the number-sign. It's part of my userid !!!)info-vax@ucbvax.ARPA (08/05/85)
From: Gail Rubin <grubin@bbn-spca> You can use batch jobs, submitted from systartup, to set up group logicals. This is the recommended approach, I believe, as opposed to detached processes. Set up a command file with the define/group or assign/group commands and submit it from systartup with: $ SUBMIT /USER=GROUP47 SYS$MANAGER:GROUP47LOGS.COM (/USER on SUBMIT is new in V4) -- Gail Rubin (grubin@bbn-spca or @bbn-unix)
info-vax@ucbvax.ARPA (08/05/85)
From: Chris Yoder <engvax!CHRIS@cit-vax>
In order to create group logical name definitions at system startup you
can use either:
$ SUBMIT /USER=GROUP47 SYS$MANAGER:LOGNAME047.COM
or
$ RUN/UIC=[47,0]/INPUT=SYS$MANAGER:LOGNAME047.COM/OUTPUT=NL: SYS$SYSTEM:LOGINOUT
The first meathod requires a bogus account with all the right privs (in
this case "GROUP47") that has to be created (unless you want to charge your
users for things run during system startup and give them privs that they may not
need.). The second meathod allows you to specify a uic that nobody owns, and
thus nobody gets charged or gets privs that they don't need and you don't have
bogus accounts sitting about (i.e. it's much cleaner). In the system managers
class that I took, the instructor recommended the RUN meathod of generating
logical names for these reasons.
-- Chris Yoder
UUCP --- {allegra|ihnp4}!scgvaxd!engvax!chris
ARPA --- engvax!chris@cit-vax.ARPA