cliff@centaure.UUCP (Clifford Dibble) (11/13/89)
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. ... [it's possible] to manage TCP/IP networks with Netview (IBM's network management product) ... IBM won't be shipping .. TCP/IP products until June 89." I'd be grateful to get more information on these products, and to hear from anyone who has actually used them. Thanks!! Cliff Dibble Irvine, CA. USA. 714-859-1172 P.D.T uunet!centaure!cliff
hughes@silver.bacs.indiana.edu (larry hughes) (11/14/89)
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. || \\=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=//
scw@ollie.SEAS.UCLA.EDU (11/14/89)
In article <29590@iuvax.cs.indiana.edu> hughes@silver.bacs.indiana.edu (larry hughes) writes: }> }> "... 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... Hmmmm, This is like saying that an interlan VAX card is not direct, or that an 'smart' card is not direct. Remember a 360/370 channel is much like a VERY smart unibus (albeit with only 256 slots on it). Just because there is some outboard processing doesn't mean that it's not direct. As an anology think of a IBM/PC (8086 flavor) attached to a Printronix P-600 printer, there is more computing_power/smarts in the printer than there is in the computer. Besides that's not really a FEP, as Series/1 terminal driver (for IXX) now that's an FEP. The 9370 CETI device is built into the processor, not attached to an external channel. ----- Stephen C. Woods; UCLA SEASNET; 2567 BH;LA CA 90024; (213)-825-8614 UUCP: ...!{ibmsupt,hao!cepu}!ollie}!scw ARPA:scw@{Ollie.,}SEAS.UCLA.EDU
NJG@CORNELLA.CIT.CORNELL.EDU (Nick Gimbrone) (11/24/89)
>In the article "OSI Takes on TCP/IP" (S.Fisher, UNIX World, Feb 1989), >it is stated: ... > ... IBM won't be shipping .. TCP/IP products until > June 89." That was only for the MVS based product. VM/CMS has had an IBM TCP/IP since mid-87. They also have several unix offerings (which clearly have tcp/ip, otherwise you couldn't really call it unix, eh? :-). In any case, for further discusion of IBM's products see the IBMTCP-L mail list at CUNYVM.CUNY.EDU, subscription by sending mail to LISTSERV@CUNYVM.CUNY.EDU w/ the one line body/text of: SUBscribe IBMTCP-L <your-name-here>