Path: utzoo!attcan!uunet!samsung!sdd.hp.com!ucsd!ucbvax!stiatl.UUCP!tom From: tom@stiatl.UUCP (Tom Wiencko) Newsgroups: comp.protocols.ibm Subject: Re: TCP/IP and SNA Message-ID: <9005311818.AA23547@lilac.berkeley.edu> Date: 4 May 90 16:32:17 GMT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Tom Wiencko Organization: The Internet Lines: 30 dboyes@RICE.EDU (David Boyes) writes: >In article <9946@stiatl.UUCP> tom@stiatl.UUCP (Tom Wiencko) writes: >>dboyes@rice.edu (David Boyes) writes: >>>as the IBM TCP product supports IP over SNA. >>Oh really? How does this work? I was told (by many, many IBMers) that >>IP cannot run over SNA links. If this is possible, I would sure like >>to know how. >The IBM TCP/IP for VM (and the MVS version, too) implementation >provides a application called SNALINK that does the encapsulation >processing and pumps it through a LU 0 VTAM connection >to a similar configuration on the other side of the SNA >connection, where the remote SNALINK machine unwraps it and does >it's thing. This would mean that there are mainframes (something running SNALINK) on the endpoints of the SNA conversation. I would have RS/6000s on at least one end of each conversation, with a 3745 attached to a 3090 acting as a central site. This would work if there was something like SNALINK for the RS/6000. Is there such a thing? Tom -- Tom Wiencko (w) (404) 977-4515 gatech!stiatl!tom Wiencko & Associates, Inc.