robin@csuchico.edu (Robin Goldstone) (09/26/90)
We are investigating TCP/IP solutions for our IBM MVS 3090 environment as well as for our VM 4381 environment. On the VM side, we have already procured IBM's TCP/IP offering and an 8232. I have been following the discussion here about IBM's TCP/IP for VM. Right now things are getting kind of heated in this discussion and I am having trouble distinguishing fact from fiction. So I think I'll skip my questions about VM TCP/IP... I do remember reading numerous complaints about the 8232 and praises about a product called the ELC from BTI. We are trying to get rid of the 8232 and replace it with something else. Should we get a BTI ELC? I also have literature on the Fibronic's K200 and K2000. Can anyone compare these products to the BTI product in terms of price/performance? On the MVS side, Fibronics has sent literature on their KNET product. How does this compare to IBM's TCP/IP offering for MVS? Are there any other players in this market? Maybe this discussion belongs in an IBM newsgroup... If so, which one? Thanks for any info you can provide. Robin Goldstone, Systems Software Specialist California State University, Chico Computing Services robin@csuchico.edu
salzman@NMS.HLS.COM (Mike Salzman) (09/26/90)
Robin at Cal State Chico asks:
.....deleted......
> I do remember reading numerous complaints about the 8232 and praises about
> a product called the ELC from BTI. We are trying to get rid of the 8232
> and replace it with something else. Should we get a BTI ELC? I also
> have literature on the Fibronic's K200 and K2000. Can anyone compare these
> products to the BTI product in terms of price/performance?
.... deleted....
>
I happened to do a market survey earlier this year among commercial users
of IBM TCP/IP solutions. They included users of IBMs software as well
as third party. The IBM 8232 came in for a lot of abuse, mainly because
of performance, not because of any serious shortcoming. Users of the BTI
product were quite happy with it. Users of other systems, including the IBM
8232, told me on two occasions that they wished they had bought it.
Recently IBM announced a new product to replace the 8232, called the 3172. It
seems to be more directly engineered for the purpose of frontending a LAN,
and appears to offer higher performance at lower cost.
I have used none of these products myself, and have no affiliations
with any of the vendors.
--
-------------------- salzman@hls.com ----------------------
Michael M. Salzman Voice (415) 966-7479 Fax (415)960-3738
Hughes Lan Systems 1225 Charleston Road Mt View Ca 94043 PMW1@psuvm.psu.edu (Peter M. Weiss) (09/26/90)
In article <1990Sep25.191233.6543@ecst.csuchico.edu>, robin@csuchico.edu (Robin Goldstone) says: (stuff deleted) >Maybe this discussion belongs in an IBM newsgroup... If so, which one? >Thanks for any info you can provide. I would like to suggest that you search the IBMTCP-L notebook archives stored on the listserv@pucc.princeton.edu. /Pete -- Peter M. Weiss | pmw1@psuvm or @vm.psu.edu 31 Shields Bldg (the AIS people) | not affiliated with PSUVM | VM.PSU.EDU University Park, PA USA 16802 | Disclaimer -* +* applies herein
scottr@npdiss1.StPaul.NCR.COM (Scott Reedstrom) (09/26/90)
In article <1990Sep25.191233.6543@ecst.csuchico.edu> robin@csuchico.edu (Robin Goldstone) writes: >How does this compare to IBM's TCP/IP offering for MVS? Are there any >other players in this market? Yes, NCR Comten came out with a TCP/IP offering. It uses the front end to run the TCP/IP protocol stack. 3270 terminals attached to the front end can run Telnet out the network connection, and Telnet connections can switch between hosts in the front end. The downside is you need to have a Comten front end. -- Scott Reedstrom | UUCP: ncrlnk!ncrstp!npdiss1!scottr NCR Network Products Division | Domain: scottr@stpaul.ncr.com St. Paul, MN 55434
salzman@NMS.HLS.COM (Mike Salzman) (09/27/90)
> > Hi Mike, > > > I happened to do a market survey earlier this year among commercial users > > of IBM TCP/IP solutions. They included users of IBMs software as well > > as third party. > > is this report general available ? If yes, could you please sent me > an electronic copy ? Thanks very much ! > > Jan Hi Jan, The survey was part of a corporate market research effort, that we undertook in the area of structured wiring systems. It happened that some of the sites which we visited were true "blue" sites, and during the conversation with them I asked about the LAN front end systems that they had. The survey was not specifically about that topic, but about their LAN plans. I became interested in the topic also because all the IBM sites indicated a strong interest in both ethernet and TCP/IP. Needless to say, I was quite surprised at these two answers, having expected to hear them say Token Ring and SNA. In any case, our study was for internal consumption, and does not shed any further light on the question raised in the mailing list about 8232 alternatives. -- -------------------- salzman@hls.com ---------------------- Michael M. Salzman Voice (415) 966-7479 Fax (415)960-3738 Hughes Lan Systems 1225 Charleston Road Mt View Ca 94043
OZGIT@TRMETU.BITNET (Attila OZGIT) (09/27/90)
Dear Robin, I am currently investigating the same topics. I posted an inquiry to BIG-LAN discussion list but not received any response as yet. Could you pls send me a copy from each reply that you receive ? Regards. Attila OZGIT Middle East Technical University Computer Center Ankara, TURKEY
vvkmj@spica.lerc.nasa.gov (Keith Jackson) (10/04/90)
NASA Lewis has the KNET product running on our VM system and from what I gather it has not been entirely happy. TCP/IP was just installed on the MVS system and the same product was also installed on VM replacing KNET. Sorry about being so vaque, but I not in charge of those systems. If you would like more info, give my a call and I can get you in touch with the appropriate system people. -- ----------------------------------------------------------------------------- Keith Jackson | phone: 216-433-5105 or Sverdrup Technology, Inc | 216-891-2946 NASA Lewis Research Center | email: vvkmj@spica.lerc.nasa.gov