Xref: utzoo comp.protocols.ibm:379 comp.dcom.lans:2151 Path: utzoo!utgpu!watmath!clyde!att!ucbvax!ucsd!rutgers!njin!gould From: gould@pilot.njin.net (Brian Jay Gould) Newsgroups: comp.protocols.ibm,comp.dcom.lans Subject: Re: TCP/IP for IBM/MVS systems Summary: Prepare for MVS sockets Keywords: ACC, MITEK, etc. Message-ID: Date: 30 Dec 88 15:10:06 GMT References: Organization: NJ InterCampus Network, New Brunswick, N.J. Lines: 28 In article , HEDGPETH.S@RWMVS.RAY.COM (Steve Hedgpeth) writes: > We are looking at some Ethernet, TCP/IP based options for providing > a terminal emulation and file transfer gateway to an existing IBM 3090 > under MVS, (no VM). We have an existing TCP/IP network with Apollos, > VMS VAXes, UNIX VAXes, Suns, C/V's, HP's, PC's, etc. > ...... > > 3. IBM has a TCP option for the IBM/MVS operating system but it is > not available until 3Q89. Their box, the 8232, is available now. > There are a number of products out there that can connect to IBM 370-series channels and something else (ethernet, pronet, token ring)... And there are a few TCP/IP packages out there. With whatever solution you pick, be sure that when full IP socket support is in MVS, the hardware you've selected will work. Get guarantees from the vendor in writing. You should probably avoid anything that does IP or (worse) TCP processing onboard. Someday, you'll want to do more than terminal emulation and file transfer. --> Any disclaimers, made by me or by anyone on my behalf, may or may not accurately represent my representation of myself or others. -- ------------------------------------------------------------------------- - Brian Jay Gould :: INTERNET gould@jvnca.csc.org BITNET gould@jvncc - - UUCP rutgers!njin!gould Telephone (201) 329-9616 - ------------------------------------------------------------------------s