Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!sitvxb.BITNET!dstevens
From: dstevens@sitvxb.BITNET.UUCP
Newsgroups: mod.computers.vax
Subject: Re: using LAT
Message-ID: <870112172656.002@sitvxb>
Date: Mon, 12-Jan-87 17:27:30 EST
Article-I.D.: sitvxb.870112172656.002
Posted: Mon Jan 12 17:27:30 1987
Date-Received: Tue, 13-Jan-87 19:05:56 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 22
Approved: info-vax@sri-kl.arpa


 What about the overhead caused by DECnet on a VMS system.   When you set host
 from any system to a VMS system the amount of overhead caused by CTERM is a
 pain (to say the least), but there is very little overhead when you LAT into
 a VAX.
 Also concider, if you have a memory poor vax, and a non-memory poor vax in a
 cluster, and users can only connect directly to the poor vax, what do they do??
 They SET HOST to the other (faster vax).  Now your fast vax is being bogged
 down by all these remote host from the other cluster node, and its no longer
 fast.


 David L. Stevens
 Stevens Institute of Technology
 [ No I'm not related to the founders of the college...I just work here. ]

 BITNET: DSTEVENS@SITVXA.BITNET
 CCnet:  DSTEVENS@SITVXA

ps: I would realy love to see SET HOST/LAT/CTERM in VMS 5.0 (hope-hope beg-beg)

pps: I also am planning on SPRing it as a suggested enhancement