Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!decvax!ucbvax!XEROX.COM!"Ken_Garnett.AYLRX" From: "Ken_Garnett.AYLRX"@XEROX.COM.UUCP Newsgroups: mod.computers.vax Subject: Re: DECserver jerky output Message-ID: <861205-015713-5762@Xerox> Date: Fri, 5-Dec-86 04:57:30 EST Article-I.D.: Xerox.861205-015713-5762 Posted: Fri Dec 5 04:57:30 1986 Date-Received: Sun, 7-Dec-86 13:00:55 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 21 Approved: info-vax@sri-kl.arpa The jerky output you are getting is probably due (as you say) to LAT11, the set host 0 will not have the same effect on the 8600 as this does not use LAT11 but the full function decnet code, I have heard other users have the same problem with both terminal access through LAT11 and X25, these protocols seem to be fine for moving large chunks of data around but not for terminal traffic where the vax can generate packets for the terminal with a very small amount of data contained in the packet (for full duplex, a packet containing one byte of user data is not unusual) this means the server has to do a phenominal amount of work dis-assembling the packets as they arrive, also the host vax is doing far more work than would be desirable. I have heard that as LAT11 is a subset of decnet that the LAT packets are treated as second rate by the host decnet software, but I have no proof of this. CURE :- sorry I know of none ! (maybe someone closer to DEC can provide an answer) Regards Ken Garnett Advanced Technology Manager, Rank Xerox, Aylesbury, UK