dbd%vx2.GBA.NYU.EDU%KL.SRI.COM%lbl%sfsu1.hepnet@LBL.GOV (05/28/88)
Received: from KL.SRI.COM by LBL.Gov with INTERNET ;
Fri, 27 May 88 03:24:10 PDT
Received: from vx2.GBA.NYU.EDU by KL.SRI.COM with TCP; Wed 25 May 88 13:20:02-PDT
Received: by vx2.GBA.NYU.EDU (5.51/) id AA00320; Wed, 25 May 88 14:38:34 EDT
Date: Wed, 25 May 1988 14:38:31 EDT
Sender: Daniel B Dobkin <dbd@vx2.GBA.NYU.EDU>
From: Daniel B Dobkin <dbd@vx2.GBA.NYU.EDU>
To: info-vax@kl.sri.com, tcp-ip@sri-nic.arpa
Subject: VMS <--> IBM connection
Message-Id: <CMM.0.86.580588711.dbd@vx2.GBA.NYU.EDU>
Here's another of those frequently asked questions; trouble is, the
information changes almost as frequently....
We are a large VAX/VMS shop looking for a way to communicate with our
IBM mainframes (MVS). We've looked quite seriously at the FLEXlink
product; what I need now is to hear from ANYONE with experience with
this product -- anything at all, from war stories to "couldn't live
without it" and whatever's in between. (For those who don't know,
FLEXlink software provides file transfer, terminal emulation, and
task-to-task capabilites through special hardware that sits between
a VAX and an IBM system.)
I'd also like to hear from anyone who's used (or is familiar with)
ACC's TCP/IP package for MVS. Are there advantages/disadvantages
to using TCP v. FLEXlink? (Yes, some are obvious.)
Please reply directly to me -- I'll be glad to summarize whatever I
get back.
thanks,
\dbd
Irving Trust Co.
dbd@gba.nyu.edu
(212) 815 3712