Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!rutgers!im4u!ut-sally!utah-cs!utah-gr!uplherc!nrc-ut!nrcvax!kvc
From: kvc@nrcvax.UUCP (Kevin Carosso)
Newsgroups: comp.sys.dec,comp.os.vms
Subject: Re: DEC/Shell and SYS$SYLOGIN clash - help
Message-ID: <1266@nrcvax.UUCP>
Date: Mon, 2-Nov-87 17:30:56 EST
Article-I.D.: nrcvax.1266
Posted: Mon Nov  2 17:30:56 1987
Date-Received: Sat, 7-Nov-87 10:20:34 EST
References: <18342@teknowledge-vaxc.ARPA> <4104@ecsvax.UUCP> <756@ritcv.UUCP>
Reply-To: kvc@minnie.UUCP (Kevin Carosso)
Organization: Network Research Corp.  Oxnard, CA
Lines: 21
Xref: mnetor comp.sys.dec:434 comp.os.vms:3378

The solution is to make sure your definition of SYS$SYLOGIN does
NOT specify a file type.  For example:

	DEFINE/SYSTEM/EXEC SYS$SYLOGIN SYS$MANAGER:SYLOGIN

If the user specifies DCL as his CLI at login time, DCL will open the
file SYS$SYLOGIN with a default file specification of ".COM", and
so will open and read SYS$MANAGER:SYLOGIN.COM

The Shell does not specify a default file specification with a file
type, and so will open and read SYS$MANAGER:SYLOGIN.

You should then create SYLOGIN.COM with appropriate DCL commands and
SYLOGIN. with appropriate Shell commands.  I assume the same would work
for MCR with SYLOGIN.CMD.

Users can also have LOGIN.COM and LOGIN. files if the LGICMD field
of their entry in SYSUAF does not specify the file type.

	/Kevin Carosso            kvc@nrcvax.uucp
	 Network Research Co.