Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!decwrl!amdcad!lll-crg!ucdavis!ucbvax!info-vax
From: info-vax@ucbvax.UUCP
Newsgroups: mod.computers.vax
Subject: Problem with async DECnet
Message-ID: <8601152031.AA12826@csvax.caltech.edu>
Date: Wed, 15-Jan-86 14:45:35 EST
Article-I.D.: csvax.8601152031.AA12826
Posted: Wed Jan 15 14:45:35 1986
Date-Received: Fri, 17-Jan-86 00:39:01 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20
Approved: info-vax@sri-kl.arpa

Mike,

The problem here is that you can't run async DECnet between two systems that
are not in the same DECnet area.  Check out the "Guide to VMS Networking",
page 5-13 under the section labeled ""Reasons for Failure of Static
Asynchronous Connections". (after the manual was updated to V4.2, this part
was not in previous incarnations of the manual, since mine has a big change
bar on the page).  Your example had one node in area 63 and the other in
area 1.

I assume this restriction has to do with the amount of traffic between area
routers being more than they want an async line to bear.  Frankly, as in
so many other things, I'd rather they let ME decide whether the usefulness
warrants the extra load.  (I need to connect two separate areas with
dynamic DECnet for very light traffic, but cannot, thanks to what appears
to be a rather arbitrary restriction.)  If there really is a sound reason
for this restriction, then I'd like to hear it.

	/Kevin Carosso                 engvax!kvc @ CIT-VAX.ARPA
	 Hughes Aircraft Co.