Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!hubcap!ncrcae!heath
From: heath@ncrcae.Columbia.NCR.COM (Robert Heath)
Newsgroups: comp.protocols.misc
Subject: Re: X.25 on a NCR Tower
Message-ID: <2648@ncrcae.Columbia.NCR.COM>
Date: Sat, 17-Oct-87 11:42:55 EDT
Article-I.D.: ncrcae.2648
Posted: Sat Oct 17 11:42:55 1987
Date-Received: Sun, 18-Oct-87 11:08:16 EDT
References: <666@rlgvax.UUCP>
Reply-To: heath@ncrcae.UUCP (Robert Heath)
Distribution: na
Organization: NCR Corp., Engineering & Manufacturing - Columbia, SC
Lines: 17
Keywords: X.25 NCR Tower

George,
	Having been involved with X.25 development on the TOWER, I
can say that you shouldn't notice any general system performance 
degradation due to addition of X.25.
Compared to disk or tape activity, the X.25 steals very little from
other processes.  The link level stuff is offloaded by a fairly smart
comm processor, while the packet level runs as an application.

The programmatic interface to the X.25 packet layer is somewhat difficult 
to understand. On the other hand, most people use it with
PAD or SNA packages, and don't see that interface.

For a write-up on the TOWER X.25 PAD product, see my article in 
the Feb. '87 issue of Data Communications magazine.
	Robert Heath
	heath@ncrcae.UUCP
	heath@ncrcae.Columbia.NCR.COM