Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Disconnect from SET HOST
Message-ID: <880705095110.182f@CitHex.Caltech.Edu>
Date: 5 Jul 88 17:04:03 GMT
References: <7896@rama.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 30


 >   Here at SC we have a number of MicroVax GPX's used for various chores.
 > Because they have no terminal lines (ignoring CSA0:, of course), most of
 > us SET HOST to use them.
 > 
 >   What I would like to do is set the remote terminal (RTAxx:) /DISCONNECT,
 > so we can disconnect while long jobs are running, and go hog some other
 > machine.  However, VMS doesn't let you set either the template device
 > (RTA0:) or your current device (RTAxx:) to /DISCONNECT.
 > 
 >   Is there any other way to do this?  It would be most handy.
 > Thanks in advance.

There's no way (at least that's what the VMS documentation said  when  virtual
terminals first came out) to make an RTxx:  disconnectable.  However, there is
a workaround for your problem (maybe).  If you set the physical  terminals  on
which  the  users log in on other machines /SECURE_SERVER/PERMANENT, then they
can hit  to do the equivalent of  DISCONNECT/CONTINUE  from  the  local
machine.   You'll still have the DECnet link between the local machine and the
GPX, so if the user reconnects to his disconnected  local  process,  he'll  be
back on the GPX.

Another alternative would be to buy a TCP/IP package for both the GPX and  the
machines  the  users  originally  log in on.  MULTINET, from SRI International
(the version of TCP/IP we run on CITHEX) has the feature that if you exit from
TELNET  without  logging  out,  the remote process is disconnected.  A word of
warning here:  if you create a disconnected process this way then  log  in  on
the  GPX  from  the  console,  it  will offer you the chance to connect to the
disconnected process.  If you accept its offer, the system will crash  (or  at
least it would under uVMS v4.4 and [I think] VWS v3.1).