🚀 go-pugleaf

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