Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!silver!hughes From: hughes@silver.bacs.indiana.edu (larry hughes) Newsgroups: comp.protocols.tcp-ip Subject: Re: Seeking info on TCP/IP for IBM m/f Keywords: TCP/IP, IBM Message-ID: <29590@iuvax.cs.indiana.edu> Date: 13 Nov 89 22:08:59 GMT References: <122@centaure.UUCP> Sender: hughes@silver.bacs.indiana.edu (larry hughes) Reply-To: hughes@silver.bacs.indiana.edu (larry hughes) Organization: Indiana University, Bloomington Lines: 34 In article <122@centaure.UUCP> cliff@centaure.UUCP (Clifford Dibble) writes: > >I'm interested in TCP/IP products for IBM mainframes. I'm taking a >"Introduction to LANs" class, and this is one area of research >suggested by the instructor. Specifically, we're to find ways to >make an Ethernet full of Sun workstations talk to an IBM >mainframe. > >In the article "OSI Takes on TCP/IP" (S.Fisher, UNIX World, Feb 1989), >it is stated: > > "... in addition, IBM extended support TCP/IP support from > its UNIX systems to its mainframes. System 370s can > communicate with devices supporting TCP/IP either by > a direct connection to an Ethernet network, or through > the 8232 LAN channel station to a token ring LAN. > Not really "direct"! IBM's TCP/IP solution calls for an industrial-strength AT that's attached to the ethernet, and channel attached back to the IBM host. They call it a FEP (front end processor). We're running an Intel FEP here... //=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\\ || Larry J. Hughes, Senior Programmer || hughes@silver.bacs.indiana.edu || || Indiana University || || || University Computing Services || "The person who knows everything || || 750 N. State Road 46 Bypass || has a lot to learn." || || Bloomington, IN 47405 || || || (812) 855-9255 || Disclaimer: See quote above. || \\=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=//