Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!NIC.DDN.MIL!tcp-ip-RELAY From: tcp-ip-RELAY@NIC.DDN.MIL Newsgroups: comp.protocols.tcp-ip Subject: (none) Message-ID: <8911140710.AA01585@ucbvax.Berkeley.EDU> Date: 14 Nov 89 07:10:42 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 152 tcp-ip-relay F4.N494.Z5.FIDONET.ORG TCP-IP-RES.RURES .WSU.EDU tcp-ip-user@CS DUPHY4.DREXEL.EDU tcp-ip-users LBL.GOV tcp-ip-users BNLUX0.BNL.GOV TCP-IP CARLETON.BITNET tcp-ip CS.MCGILL.CA TCP-IP MSSTATE.EDU TCP-IP NET.NRL.NAVY.MIL tcp-ip NETLABS.COM tcp-ip RIACS.EDU TCP-IP SPAM.ISTC.SRI.COM tcp-ip SCCGATE.SCC.COM tcp-ip TWG.COM tcp-ip USAFA.AF.MIL tcp-ip USNA.USNA.NAVY.MIL tcp-ip UTDALVM1.UTDALLAS.EDU tcp-ip UV4.EGLIN.AF.MIL TCP-IP VAX01.AMS.COM TCP-IP VENERA.ISI.EDU TCP-IP XX.DREA.DND.CA TCP-IP mbunix.mitre.org tcp-ips PURDUE.EDU tcp-ip-local MDC.COM tcp-ip-relay XEROX.COM tcp-ip^.x INTERLAN.COM tcp-sig TRWIND.TRW.COM tcp saturn.acc.com tcpip-col OMNIGATE.CLARKSON.EDU tcpip-local ALDNCF.ALCOA.COM tcpip CAM.UNISYS.COM tcpip SED.CEEE.NIST.GOV tcpip SIMPACT.COM tcpip CIM-VAX.HONEYWELL.COM tcpip isdres.isd.usgs.gov tcpip LOGICON.ARPA tcpip muvms1.bitnet tcpip anes.ucla.edu tcp-ipg ncs.dnd.ca tcpipinfo MSR.EPM.ORNL.GOV tcpnews WLV.IMSD.CONTEL.COM teecp-ip HAC2ARPA.HAC.COM thomson%aries DTRC.ARPA tinker CTS.SRI.COM tony FORALIE.ICS.HAWAII.EDU torben USC-SCE.USC.EDU tsudik CSAM.LBL.GOV van GARGOYLE.UCHICAGO.EDU vijit!tcplist DUCVAX.AUBURN.EDU warlick CSLI.STANFORD.EDU whp4 NARDACVA.ARPA yx0quinn Received: from ucbvax.Berkeley.EDU by NIC.DDN.MIL with TCP; Mon, 13 Nov 89 14:21:58 PST Received: by ucbvax.Berkeley.EDU (5.61/1.39) id AA28347; Mon, 13 Nov 89 14:10:25 -0800 Received: from USENET by ucbvax.Berkeley.EDU with netnews for tcp-ip@sri-nic.arpa (tcp-ip@sri-nic.arpa) (contact usenet@ucbvax.Berkeley.EDU if you have questions) Date: 13 Nov 89 22:08:59 GMT From: silver!hughes@iuvax.cs.indiana.edu (larry hughes) Organization: Indiana University, Bloomington Subject: Re: Seeking info on TCP/IP for IBM m/f Message-Id: <29590@iuvax.cs.indiana.edu> References: <122@centaure.UUCP> Sender: tcp-ip-relay@NIC.DDN.MIL To: tcp-ip@NIC.DDN.MIL 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. || \\=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=//