Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ucbcad!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: DEC/Shell and SYS$SYLOGIN clash - help
Message-ID: <871102145840.08n@CitHex.Caltech.Edu>
Date: Mon, 2-Nov-87 18:08:31 EST
Article-I.D.: CitHex.871102145840.08n
Posted: Mon Nov  2 18:08:31 1987
Date-Received: Sat, 7-Nov-87 16:50:54 EST
References: <4104@ecsvax.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 48


 > In article <18342@teknowledge-vaxc.ARPA>, mkhaw@teknowledge-vaxc.ARPA (Mike Khaw) writes:
 > > We have a VMS 4.5 system on which some users want to run DEC/Shell as
 > > their default CLI, while most users want to run DCL.  The problem is
 > > how to make the system not try to execute SYS$SYLOGIN when a DEC/Shell
 > > user logs in.  Anyone know a solution?  We don't want to get rid of
 > > SYS$SYLOGIN since it does a lot of useful things for DCL users, but it
 > > makes DEC/Shell barf and therefore fail to execute the user's private
 > > shell startup file (.profile)
 > > 
 > > Thanks,
 > > Mike Khaw
 > > -- 
 >   
 >      Your problem is very simple... Go into the authorize utility, and
 > set all DEC Shell users lgicmd to be something (or nothing!) other then 
 > mgr$login (which is a logical that points to syslogin.com).  Our
 > DEC Shell users have lgicmd set to .PROFILE  (which is what dec
 > suggests).  They have a file called .PROFILE in their sys$login
 > directory (naturally!), with Shell commands.  All of this is modeled 
 > somewhat after unix I suppose.  
 >      Hope this helps!
 > 
 >               Mark Cooperstein
 >                    NCSU School of Veterinary Medicine
 >                    Raleigh  NC
   
It's rather unlikely to help, since it's dead wrong.  The LGICMD field in
SYSUAF.DAT specifies the procedure to be executed AFTER SYS$SYLOGIN: is
executed.  Thus, changing that entry WILL NOT solve the problem described
in the original posting.  The following suggestion is possibly wrong, since
I don't have a machine with DECshell that I can test it on:

	If I recall correctly, if DECshell is told to execute a procedure,
	and the filename specified has no extension, DECshell will look
	for the file with no extension; DCL, on the other hand will look
	for the file with a .COM extension.  Thus, I suspect your problem
	may be that you've got SYS$SYLOGIN defined to be something like
	SYS$MANAGER:LOGIN.COM, which forces both DCL and DECshell to execute
	the .COM file.  If DECshell behaves the way I think it does, you
	could instead define SYS$SYLOGIN to be, say, SYS$MANAGER:LOGIN
	Then you could put the standard DCL startup commands in the file
	SYS$MANAGER:LOGIN.COM, and the standard DECshell commands in the
	file SYS$MANAGER:LOGIN., and both classes of users would be happy.

Again, the above suggestion is made on the basis of my recollections of
DECshell behavior, and may not work: don't just do as I suggest without
checking to make sure things work the way you want them to.