Path: utzoo!attcan!uunet!husc6!mailrus!ames!pasteur!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: SET HOST Problem
Message-ID: <880805043007.803@CitHex.Caltech.Edu>
Date: 5 Aug 88 11:43:40 GMT
References: <5202@watcgl.waterloo.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 28


 > I'm having a problem with the SET HOST command.  Our uVAX II
 > (VMS 4.7) is connected to a dozen non-VMS computers, and I want
 > to connect my VT220 terminal to any of those systems.  The command
 > 
 > 	$ SET HOST/DTE $TERMINAL1
 > 
 > works fine at the VMS level (i.e. my VT220 becomes a terminal
 > for the remote machine).  The problem is that it doesn't work
 > from within a command (DCL) file.  It exits with the message:
 > 
 > 	%REM-F-NOTERM, command device is not a terminal
 >
 > I want to do it from DCL because I would like to put up a menu of the
 > systems the user can connect to.
 > 
 > Note the /DTE (Data Terminal Equipment) option - I think that this is
 > causing the problem.  (A friend of mine tried "SET HOST" (no /DTE)
 > on his machine to another VMS machine over DECnet, and it works okay).

SET HOST used to do the same thing before they invented SET HOST/DTE.  The
problem is that SET HOST/DTE wants to talk to you via the file SYS$INPUT.
When you execute a DCL procedure from an interactive job, that procedure
becomes SYS$INPUT.  Your terminal remains SYS$COMMAND.  The workaround is
to redirect SYS$INPUT before activating the image.  The following works:

	$ DEFINE/USER_MODE SYS$INPUT SYS$COMMAND
 	$ SET HOST/DTE $TERMINAL1