Article View: comp.protocols.ibm
Article #858Re: Mainframe I/O channel <--> PC/UNIX/LAN
From: hank
Date: Sun, 27 Jan 1991 03:38
Date: Sun, 27 Jan 1991 03:38
34 lines
2404 bytes
2404 bytes
In article <22860@well.sf.ca.us> ericsm@well.sf.ca.us (Eric Smith) writes:
>
>Does anyone reading this know if there is a better solution to this? I
>want to find alternatives to KMW/Auscom, just so we can compare
>products and see if we are getting the most cost effective. We want to
>keep using the direct connection to the mainframe I/O channel, because
>we don't want to change the mainframe software, but we are willing to
>change the Unix and/or PC software.
The most efficient way is getting a channel attach to the mainframe,
although it can be an expensive solution.
An alternative is to get a token ring card and connect to the 3174 controller
(assuming you have more recent controllers with token ring built-in).
AT&T sells a SNA/LINK package that can handle that. The bonus is that you
can also access the mainframe from your ascii terminal. The draw back is
that the package is using IND$FILE for file transfer which runs like a pig
(we have timed it running at an effective rate of ~1000 bit/sec at an 56Kb
attach). The same package can also handle remote connection through lease
line or modem if you use an intellegent serial card instead of a token ring
adaptor. You do not any special software on the mainframe except IND$FILE
which is rather standard on most system supporting file transfer (particularly
mainframe to PC).
I also heard of ethernet TCP/IP type connections. They are basically an
(overpriced, IMHO) UNIX box one end connecting to the mainframe
(typically channel attach) and another end connect to ethernet.
However, these are usually very expensive solutions (expensive box and
expensive mainfame software).
--
Peter Yeung Amdahl Canada Ltd., Software Development Center
2000 Argentia Road, Plaza 2, Suite 300
Mississauga, Ont. L5N 1V8
Phone: (416) 542-6300 Fax: (416) 858-2233
Technical Details
Message-ID:
<9101271006.AA11279@lilac.berkeley.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!magnus.ircc.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!bitnic.BITNET!hankShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!magnus.ircc.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!bitnic.BITNET!hank From: hank@bitnic.BITNET Newsgroups: comp.protocols.ibm Subject: Re: Mainframe I/O channel <--> PC/UNIX/LAN Message-ID: <9101271006.AA11279@lilac.berkeley.edu> Date: 27 Jan 91 03:38:57 GMT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: hank%bitnic.BITNET@lilac.berkeley.edu Organization: The Internet Lines: 34