🚀 go-pugleaf

>> 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)
>> 
>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.  

Wrong:

	The behavior of LOGINOUT is to attempt to run the procedure
pointed to by the logical name SYS$SYLOGIN and THEN run the procedure
specified in the authorize field LGICMD.  (This changed in VMS from V2 to
V3). If SYS$SYLOGIN does not translate then LOGINOUT goes directly to
the LGICMD specified procedure.  IF the UAF field LGICMD is blank
as the default record is normally then LOGINOUT does a simple @LOGIN
(or equivilant for the DEC shell I would assume)  In our 2 CLI shop
(DCL and MCR) this results in either LOGIN.COM or LOGIN.CMD being
run depending on the CLI. (.CMD is what MCR wants).  We have
the logical name SYS$SYLOGIN ( $ DEFINE/EXEC natch) pointing to
the file SYS$MANAGER:SYLOGIN.  Note: NO .COM extension on the
logical name.  we then have SYLOGIN.COM (DCL) and SYLOGIN.CMD (MCR) flavors
of our system login routines.

I assume a similar action can happen with DECshell. SYLOGIN.PROFILE maybe?
If not. I would  set up a SYLOGIN.COM that has a command that will do
2 actions depending on whether it is running DCL or SHELL. If it
is a DCL command then it would be a No operation command.  If it was
under DECshell then it would run some shell script and exit. 

- Andrew W. Potter
- Rochester Institute of Technology