home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.modems
- Path: sparky!uunet!sun-barr!ames!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!gateway.univel.com!ns.novell.com!gateway.novell.com!thisbe!terry
- From: terry@thisbe.npd.Novell.COM (Terry Lambert)
- Subject: Re: Binary Sychronous Communication (2780)
- Message-ID: <1992Sep4.200528.13017@gateway.novell.com>
- Sender: terry@thisbe (Terry Lambert)
- Nntp-Posting-Host: thisbe.eng.sandy.novell.com
- Organization: Novell NPD -- Sandy, UT
- References: <1992Sep4.165109.10091@ramsey.cs.laurentian.ca>
- Date: Fri, 4 Sep 1992 20:05:28 GMT
- Lines: 30
-
- In article <1992Sep4.165109.10091@ramsey.cs.laurentian.ca>, eastick@ramsey.cs.laurentian.ca (Doug Eastick) writes:
- |>
- |> We are in the position of having to dial-up an IBM mainframe to pick up
- |> some EDI documents. We'd like to use an intel x86 box. I know of a board
- |> from Cleo Communications which will give us bisync and will work with
- |> various DOS software communication packages.
- |>
- |> My question is this: does anyone know of any 386, UNIX-based or UNIX-like
- |> OS's which support bisync communication? Specifically maybe BSD/386 from
- |> BSD Inc.
- |>
- |> Also, how does Telebit's T2500 do SNA and bisync when there is only an
- |> RS232 port? Hmm?
-
- The same way Blackbox Inc. does: By emulating a terminal (Ususally a 3101) in
- what they call "a protocol converter". The box then expects to talk to one of
- several terminal types via RS232C.
-
- Another possibility is TN3270, a 3270 emulator expecting a telnet like connection
- to the IBM, which then goes into 3270 "mode". This implies an ethernet port
- on your IBM and appropriate software.
-
-
- Terry Lambert
- terry_lambert@gateway.novell.com
- terry@icarus.weber.edu
-
- ---
- Disclaimer: Any opinions in this posting are my own and not those of
- my present or previous employers.
-