freeman-andrew@CS.YALE.EDU (Andrew C. Freeman) (09/15/89)
We need some advice on a couple of issues. Any comments or information
would be greatly appreciated.
Location 1: Sun 4/390s running a Sybase server
Locations 2,3,4,5: Small Sun networks across the country
What we hope to accomplish is the following:
Transparent client access from locations 2-5 to the server at
location 1 (i.e. ability to use Sybase as if we were one local net),
as well as telnet, etc.
At our disposal is an SNA network connecting all the sites. We would prefer
to use it but if there are other cost effective ways we will certainly
consider them. The real questions here are whether TCP/IP over SNA is
possible/feasible/tolerable and whether Sybase DB-library functions well
over an internet
A side issue involves SNA on Sun. Can we support a user (either logged in
via telnet to the server or directly from locations 2-5) who wants a
terminal session to an IBM host on the SNA network and can we support
application to application from the Sun server to the IBM host.
Thanks in advance for those copious, informative replies. Please reply by
mail and include a telephone number if you would'nt mind a phone call. Also,
I realize that these topics may be fairly standard to some but please, don't
let my ignorance dissuade you from replying.
Thanks,
Andrew
freeman-andrew@CS.YALE.EDU ("Andrew C. Freeman") (09/15/89)
We need some advice on a couple of issues. Any comments or information
would be greatly appreciated.
Location 1: Sun 4/390s running a Sybase server
Locations 2,3,4,5: Small Sun networks across the country
What we hope to accomplish is the following:
Transparent client access from locations 2-5 to the server at
location 1 (i.e. ability to use Sybase as if we were one local net),
as well as telnet, etc.
At our disposal is an SNA network connecting all the sites. We would prefer
to use it but if there are other cost effective ways we will certainly
consider them. The real questions here are whether TCP/IP over SNA is
possible/feasible/tolerable and whether Sybase DB-library functions well
over an internet
A side issue involves SNA on Sun. Can we support a user (either logged in
via telnet to the server or directly from locations 2-5) who wants a
terminal session to an IBM host on the SNA network and can we support
application to application from the Sun server to the IBM host.
Thanks in advance for those copious, informative replies. Please reply by
mail and include a telephone number if you would'nt mind a phone call. Also,
I realize that these topics may be fairly standard to some but please, don't
let my ignorance dissuade you from replying.
Thanks,
Andrewdrake@ibmarc.uucp (Sam Drake) (09/19/89)
This isn't a commercial, but ... IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks, and there's a PRPQ available from IBM to allow the RT to do the same. Sam Drake / IBM Almaden Research Center
drake@ibmarc.UUCP (Sam Drake) (09/19/89)
This isn't a commercial, but ... IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks, and there's a PRPQ available from IBM to allow the RT to do the same. Sam Drake / IBM Almaden Research Center
robert@peregrine.peregrine.com (Robert Young) (09/25/89)
In article <1079@ks.UUCP> drake@ibmarc.UUCP (Sam Drake) writes: >This isn't a commercial, but ... > >IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks, >and there's a PRPQ available from IBM to allow the RT to do the same. > >Sam Drake / IBM Almaden Research Center I have a Sequent system (S81) connected to our 4381 mainframe through SNA. We have already purchased the TCP/IP tapes from IBM but are waiting for a hardware solution to connect the two systems. Initially, someone in technical marketing (IBM) suggested we use an RT and a token-ring to ethernet router but the idea never cooked. Now they are suggesting some type of channel attached device (Ethernet) to connect the two systems. Any ideas, suggestions and/or comments? So far it looks like the IBM people we deal with are not completely sure about any clear solutions. Any clues would really be appreciated. Robert Young Peregrine Systems
robert@peregrine.UUCP (Robert Young) (09/25/89)
In article <1079@ks.UUCP> drake@ibmarc.UUCP (Sam Drake) writes: >This isn't a commercial, but ... > >IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks, >and there's a PRPQ available from IBM to allow the RT to do the same. > >Sam Drake / IBM Almaden Research Center I have a Sequent system (S81) connected to our 4381 mainframe through SNA. We have already purchased the TCP/IP tapes from IBM but are waiting for a hardware solution to connect the two systems. Initially, someone in technical marketing (IBM) suggested we use an RT and a token-ring to ethernet router but the idea never cooked. Now they are suggesting some type of channel attached device (Ethernet) to connect the two systems. Any ideas, suggestions and/or comments? So far it looks like the IBM people we deal with are not completely sure about any clear solutions. Any clues would really be appreciated. Robert Young Peregrine Systems
kevin@msa3b.UUCP (Kevin P. Kleinfelter) (09/26/89)
robert@peregrine.UUCP (Robert Young) writes: >In article <1079@ks.UUCP> drake@ibmarc.UUCP (Sam Drake) writes: >>This isn't a commercial, but ... >> >>IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks, >>and there's a PRPQ available from IBM to allow the RT to do the same. >> >>Sam Drake / IBM Almaden Research Center [Stuff about connections suggested by IBM omitted.] >So far it looks like the IBM people we deal with are not completely sure >about any clear solutions. >Any clues would really be appreciated. O.K. I have spent quit a bit of time hashing this out with many different people, and this is how it looks to me: 1. You CAN send TCP/IP over SNA -- in SOME cases. To attach SNA to TCP/IP (using AVAILABLE hardware/software) you MUST have a host (i.e. a 370) and a host adapter (I think it is an 8232). To route TCP/IP over SNA would look as follows: workstation---8232--370====(SNA NETW)===370--8232---workstation There are plans involving RT's and SDLC links, but they do not seem (to me) to really be routing TCP/IP over an SNA network. 2. The "normal" IBM communications hardware (3705, 3174, etc) do not support TCP/IP connections. You have to attach to a host at each end of your link. Future versions of the 3705 and 3174 will probably support TCP/IP, according to an IBM employee I met at an IBM class, but that is "unofficial." 3. We don't like the above. We are looking at multiplexing TCP/IP and SNA over our existing lines, or using an X.25 service, or using other alternatives to running TCP/IP over SNA. If you find a better solution, PLEASE POST! (Other people seem to be interested!) -- Kevin Kleinfelter @ Management Science America, Inc (404) 239-2347 gatech!nanovx!msa3b!kevin
kevin@msa3b.UUCP ("Kevin P. Kleinfelter") (09/26/89)
robert@peregrine.UUCP (Robert Young) writes: >In article <1079@ks.UUCP> drake@ibmarc.UUCP (Sam Drake) writes: >>This isn't a commercial, but ... >> >>IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks, >>and there's a PRPQ available from IBM to allow the RT to do the same. >> >>Sam Drake / IBM Almaden Research Center [Stuff about connections suggested by IBM omitted.] >So far it looks like the IBM people we deal with are not completely sure >about any clear solutions. >Any clues would really be appreciated. O.K. I have spent quit a bit of time hashing this out with many different people, and this is how it looks to me: 1. You CAN send TCP/IP over SNA -- in SOME cases. To attach SNA to TCP/IP (using AVAILABLE hardware/software) you MUST have a host (i.e. a 370) and a host adapter (I think it is an 8232). To route TCP/IP over SNA would look as follows: workstation---8232--370====(SNA NETW)===370--8232---workstation There are plans involving RT's and SDLC links, but they do not seem (to me) to really be routing TCP/IP over an SNA network. 2. The "normal" IBM communications hardware (3705, 3174, etc) do not support TCP/IP connections. You have to attach to a host at each end of your link. Future versions of the 3705 and 3174 will probably support TCP/IP, according to an IBM employee I met at an IBM class, but that is "unofficial." 3. We don't like the above. We are looking at multiplexing TCP/IP and SNA over our existing lines, or using an X.25 service, or using other alternatives to running TCP/IP over SNA. If you find a better solution, PLEASE POST! (Other people seem to be interested!) -- Kevin Kleinfelter @ Management Science America, Inc (404) 239-2347 gatech!nanovx!msa3b!kevin
philf@xymox.metaphor.com (Phil Fernandez) (09/26/89)
In article <8909250654.AA16455@jade.berkeley.edu> Robert Young writes: >I have a Sequent system (S81) connected to our 4381 mainframe through >SNA. We have already purchased the TCP/IP tapes from IBM but are waiting >for a hardware solution to connect the two systems. Initially, someone in >technical marketing (IBM) suggested we use an RT and a token-ring to >ethernet router but the idea never cooked. Now they are suggesting some >type of channel attached device (Ethernet) to connect the two systems. >Any ideas, suggestions and/or comments? IBM sells a box called the 8232, which is an industrially-packaged PC/AT with one or more net interface boards (Ethernet and/or Token Ring) plus one ore more channel interface boards. It is their current standard offering for host-attach to Ethernet, and is fully supported by the mainframe-based TCP/IP software. I had some experience with this box when I used to work at Stanford; for the most part it works pretty well. With the 8232, you can just put the 4381 onto your Ethernet in just the same way you'd attach any other workstation or mini. >So far it looks like the IBM people we deal with are not completely sure >about any clear solutions. I can't resist a little bit of IBM-bashing in this case. The IBM sales and systems engineering force is just not up-to-speed on the TCP/IP and Ethernet product offerings for VM or MVS. When I was working at Stanford, IBM was trying to sell us TCP/IP software for a 3090 running MVS. They kept trotting in more senior "experts," up to the level of a "Regional Networking Specialist." Each of them spouted so much silly or plain false nonsense about TCP/IP that I could barely sit through the meetings. This lack of marketing commitment would really scare me about becoming too depending on an IBM TCP/IP solution for a S/370 system. (This are purely my own opinions, and do not reflect those of my employer) +-----------------------------+----------------------------------------------+ | Phil Fernandez | philf@metaphor.com | | | ...!{apple|decwrl}!metaphor!philf | | Metaphor Computer Systems |"Does the body rule the mind, or does the mind| | Mountain View, CA | rule the body? I dunno..." - Morrissey | +-----------------------------+----------------------------------------------+
johnny@edvvie.at (Johann Schweigl) (09/26/89)
From article <8909190654.AA06021@jade.berkeley.edu>, by drake@ibmarc.UUCP (Sam Drake): > IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks, > and there's a PRPQ available from IBM to allow the RT to do the same. I tried to reach you by email, but something went wrong. So I am going this way. My apologies to those I bother with this text. I would like to get more Information on the RPQ for the RT, it is not in my list of currently available RPQ's. My task is to connect two RT's, both with AIX 2.2.1. One of them talks over a sync line to a 3745, currently using Network 3270/SNA. The other one is in a token ring, to which the 3745 mentioned above is also connected. In the background is a 3090/40E with MVS/ESA, but no TCP/IP installed. Both RT's act as a router into a local TCP/IP-net. 1) What's the number of the RPQ? 2) Can it be done? 3) What have I to do/buy/install to achieve a TCP/IP connection between both RT's? 4) If TCP/IP can go into SNA over the sync line, can the line be shared between the TCP/IP transporter and the 3270 emulation? Thanks, johnny -- ------------------------------------------------------------------ EDV Ges.m.b.H Vienna Johann Schweigl Hofmuehlgasse 3 - 5 USENET: johnny@edvvie.at A-1060 Vienna, Austria Tel: (0043) (222) 59907 257 (8-19 CET)
johnny@eliza.UUCP (Johann Schweigl) (09/26/89)
From article <8909190654.AA06021@jade.berkeley.edu>, by drake@ibmarc.UUCP (Sam
Drake):
> IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks,
> and there's a PRPQ available from IBM to allow the RT to do the same.
I tried to reach you by email, but something went wrong.
So I am going this way. My apologies to those I bother with this text.
I would like to get more Information on the RPQ for the RT, it is
not in my list of currently available RPQ's.
My task is to connect two RT's, both with AIX 2.2.1.
One of them talks over a sync line to a 3745, currently using Network 3270/SNA.
The other one is in a token ring, to which the 3745 mentioned above is
also connected.
In the background is a 3090/40E with MVS/ESA, but no TCP/IP installed.
Both RT's act as a router into a local TCP/IP-net.
1) What's the number of the RPQ?
2) Can it be done?
3) What have I to do/buy/install to achieve a TCP/IP connection between both
RT's?
4) If TCP/IP can go into SNA over the sync line, can the line be shared between
the TCP/IP transporter and the 3270 emulation?
Thanks, johnny
--
------------------------------------------------------------------
EDV Ges.m.b.H Vienna Johann Schweigl
Hofmuehlgasse 3 - 5 USENET: johnny@edvvie.at
A-1060 Vienna, Austria Tel: (0043) (222) 59907 257 (8-19 CET)John_Robert_Breeden@cup.portal.com (09/27/89)
>>This isn't a commercial, but ... >> >>IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks, >>and there's a PRPQ available from IBM to allow the RT to do the same. >> >>Sam Drake / IBM Almaden Research Center > >I have a Sequent system (S81) connected to our 4381 mainframe through >SNA. We have already purchased the TCP/IP tapes from IBM but are waiting >for a hardware solution to connect the two systems. Initially, someone in >technical marketing (IBM) suggested we use an RT and a token-ring to >ethernet router but the idea never cooked. Now they are suggesting some >type of channel attached device (Ethernet) to connect the two systems. >Any ideas, suggestions and/or comments? > >So far it looks like the IBM people we deal with are not completely sure >about any clear solutions. > >Any clues would really be appreciated. > >Robert Young >Peregrine Systems Anybody had experience with this box? Might it work in this case? What MITEK provides, is a box which can be either remote or channel attached to the host, and connected to our TCP network via the usual drop cable and transceiver. This box supports up to 64 concurrent login sessions, both inbound to the mainframe from the 3B2, or OUTBOUND from the mainframe to the 3b2. An SNA user looks like a vt100 to the 3b2, and 3b users look just like an IBM 32xx terminal to VTAM. File transfer is supported through FTP, and the MITEK box has complete terminal mapping and pro- grammable keyboard mapping tables. We are just completing the installation here, and our customer is very pleased both with the solution (it requires no changes to their existing network) and with the MITEK support. I am told by MITEK that they will soon (2Q89) be announcing another MITEK box which will provide the same file transfer and full-screen terminal session capability for IBM S36/38 systems and TCP/IP. If the present is any indicator, this future product should be slick. MITEK does have regional people scattered around the country, but your best bet would be to give them a call in Carrollton, and find out more about it. I hope this info helps somebody. john _robert_breeden@cup.portal.com
John_Robert_Breeden@cup.portal.COM (09/27/89)
>>This isn't a commercial, but ... >> >>IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks, >>and there's a PRPQ available from IBM to allow the RT to do the same. >> >>Sam Drake / IBM Almaden Research Center > >I have a Sequent system (S81) connected to our 4381 mainframe through >SNA. We have already purchased the TCP/IP tapes from IBM but are waiting >for a hardware solution to connect the two systems. Initially, someone in >technical marketing (IBM) suggested we use an RT and a token-ring to >ethernet router but the idea never cooked. Now they are suggesting some >type of channel attached device (Ethernet) to connect the two systems. >Any ideas, suggestions and/or comments? > >So far it looks like the IBM people we deal with are not completely sure >about any clear solutions. > >Any clues would really be appreciated. > >Robert Young >Peregrine Systems Anybody had experience with this box? Might it work in this case? What MITEK provides, is a box which can be either remote or channel attached to the host, and connected to our TCP network via the usual drop cable and transceiver. This box supports up to 64 concurrent login sessions, both inbound to the mainframe from the 3B2, or OUTBOUND from the mainframe to the 3b2. An SNA user looks like a vt100 to the 3b2, and 3b users look just like an IBM 32xx terminal to VTAM. File transfer is supported through FTP, and the MITEK box has complete terminal mapping and pro- grammable keyboard mapping tables. We are just completing the installation here, and our customer is very pleased both with the solution (it requires no changes to their existing network) and with the MITEK support. I am told by MITEK that they will soon (2Q89) be announcing another MITEK box which will provide the same file transfer and full-screen terminal session capability for IBM S36/38 systems and TCP/IP. If the present is any indicator, this future product should be slick. MITEK does have regional people scattered around the country, but your best bet would be to give them a call in Carrollton, and find out more about it. I hope this info helps somebody. john _robert_breeden@cup.portal.com
mercer@ncrcce.StPaul.NCR.COM (Dan Mercer) (09/28/89)
In article <8909261253.AA07662@jade.berkeley.edu> "Kevin P. Kleinfelter" <emcard!wa4mei!nanovx!msa3b!kevin@GATECH.EDU> writes: :robert@peregrine.UUCP (Robert Young) writes: : :>In article <1079@ks.UUCP> drake@ibmarc.UUCP (Sam Drake) writes: :>>This isn't a commercial, but ... :>> :>>IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks, :>>and there's a PRPQ available from IBM to allow the RT to do the same. :>> :>>Sam Drake / IBM Almaden Research Center : :[Stuff about connections suggested by IBM omitted.] : :>So far it looks like the IBM people we deal with are not completely sure :>about any clear solutions. :>Any clues would really be appreciated. : :O.K. I have spent quit a bit of time hashing this out with many different :people, and this is how it looks to me: : :1. You CAN send TCP/IP over SNA -- in SOME cases. : To attach SNA to TCP/IP (using AVAILABLE hardware/software) you : MUST have a host (i.e. a 370) and a host adapter (I think it is an : 8232). To route TCP/IP over SNA would look as follows: : :workstation---8232--370====(SNA NETW)===370--8232---workstation : :There are plans involving RT's and SDLC links, but they do not seem :(to me) to really be routing TCP/IP over an SNA network. : :2. The "normal" IBM communications hardware (3705, 3174, etc) do : not support TCP/IP connections. You have to attach to a host : at each end of your link. Future versions of the 3705 and 3174 : will probably support TCP/IP, according to an IBM employee : I met at an IBM class, but that is "unofficial." : :3. We don't like the above. We are looking at multiplexing TCP/IP and : SNA over our existing lines, or using an X.25 service, or : using other alternatives to running TCP/IP over SNA. If you find : a better solution, PLEASE POST! (Other people seem to be interested!) : :-- :Kevin Kleinfelter @ Management Science America, Inc (404) 239-2347 :gatech!nanovx!msa3b!kevin Try talking to your local NCR Comten representative for solutions to SNA and non-SNA networking problems. NCR Comten manufactures IBM plug compatible SNA front ends offering both channel and SDLC link attached connectivity. NCR Comten also has a wide ranging offering of connectivity products for non-SNA networks, connecting to both BSC and X.25 hosts. NCR Comten will shortly be offering a TCP-IP product. Initial link connectivity will be via X.25, but an Ethernet interface will also be provided. Your NCR Comten representative should be able to provide you with availability dates. -- Dan Mercer Reply-To: mercer@ncrcce.StPaul.NCR.COM (Dan Mercer)
mercer@ncrcce.UUCP (Dan Mercer) (09/28/89)
In article <8909261253.AA07662@jade.berkeley.edu> "Kevin P. Kleinfelter" <emcard!wa4mei!nanovx!msa3b!kevin@GATECH.EDU> writes: :robert@peregrine.UUCP (Robert Young) writes: : :>In article <1079@ks.UUCP> drake@ibmarc.UUCP (Sam Drake) writes: :>>This isn't a commercial, but ... :>> :>>IBM's VM and MVS TCP/IP products can transport TCP/IP over SNA networks, :>>and there's a PRPQ available from IBM to allow the RT to do the same. :>> :>>Sam Drake / IBM Almaden Research Center : :[Stuff about connections suggested by IBM omitted.] : :>So far it looks like the IBM people we deal with are not completely sure :>about any clear solutions. :>Any clues would really be appreciated. : :O.K. I have spent quit a bit of time hashing this out with many different :people, and this is how it looks to me: : :1. You CAN send TCP/IP over SNA -- in SOME cases. : To attach SNA to TCP/IP (using AVAILABLE hardware/software) you : MUST have a host (i.e. a 370) and a host adapter (I think it is an : 8232). To route TCP/IP over SNA would look as follows: : :workstation---8232--370====(SNA NETW)===370--8232---workstation : :There are plans involving RT's and SDLC links, but they do not seem :(to me) to really be routing TCP/IP over an SNA network. : :2. The "normal" IBM communications hardware (3705, 3174, etc) do : not support TCP/IP connections. You have to attach to a host : at each end of your link. Future versions of the 3705 and 3174 : will probably support TCP/IP, according to an IBM employee : I met at an IBM class, but that is "unofficial." : :3. We don't like the above. We are looking at multiplexing TCP/IP and : SNA over our existing lines, or using an X.25 service, or : using other alternatives to running TCP/IP over SNA. If you find : a better solution, PLEASE POST! (Other people seem to be interested!) : :-- :Kevin Kleinfelter @ Management Science America, Inc (404) 239-2347 :gatech!nanovx!msa3b!kevin Try talking to your local NCR Comten representative for solutions to SNA and non-SNA networking problems. NCR Comten manufactures IBM plug compatible SNA front ends offering both channel and SDLC link attached connectivity. NCR Comten also has a wide ranging offering of connectivity products for non-SNA networks, connecting to both BSC and X.25 hosts. NCR Comten will shortly be offering a TCP-IP product. Initial link connectivity will be via X.25, but an Ethernet interface will also be provided. Your NCR Comten representative should be able to provide you with availability dates. -- Dan Mercer Reply-To: mercer@ncrcce.StPaul.NCR.COM (Dan Mercer)
mercer@ncrcce.StPaul.NCR.COM (Dan Mercer) (09/28/89)
In article <8909261335.AA08004@jade.berkeley.edu> Phil Fernandez <metaphor!xymox!philf@APPLE.COM> writes: :In article <8909250654.AA16455@jade.berkeley.edu> Robert Young writes: :>I have a Sequent system (S81) connected to our 4381 mainframe through :>SNA. We have already purchased the TCP/IP tapes from IBM but are waiting :>for a hardware solution to connect the two systems. Initially, someone in :>technical marketing (IBM) suggested we use an RT and a token-ring to :>ethernet router but the idea never cooked. Now they are suggesting some :>type of channel attached device (Ethernet) to connect the two systems. :>Any ideas, suggestions and/or comments? : :IBM sells a box called the 8232, which is an industrially-packaged :PC/AT with one or more net interface boards (Ethernet and/or Token Ring) :plus one ore more channel interface boards. It is their current :standard offering for host-attach to Ethernet, and is fully supported :by the mainframe-based TCP/IP software. I had some experience with :this box when I used to work at Stanford; for the most part it works :pretty well. With the 8232, you can just put the 4381 onto your :Ethernet in just the same way you'd attach any other workstation or :mini. : :>So far it looks like the IBM people we deal with are not completely sure :>about any clear solutions. : :I can't resist a little bit of IBM-bashing in this case. The IBM :sales and systems engineering force is just not up-to-speed on the :TCP/IP and Ethernet product offerings for VM or MVS. When I was :working at Stanford, IBM was trying to sell us TCP/IP software for a :3090 running MVS. They kept trotting in more senior "experts," up to :the level of a "Regional Networking Specialist." Each of them spouted :so much silly or plain false nonsense about TCP/IP that I could barely :sit through the meetings. : :This lack of marketing commitment would really scare me about becoming :too depending on an IBM TCP/IP solution for a S/370 system. : :(This are purely my own opinions, and do not reflect those of my employer) : : :+-----------------------------+----------------------------------------------+ :| Phil Fernandez | philf@metaphor.com | :| | ...!{apple|decwrl}!metaphor!philf | :| Metaphor Computer Systems |"Does the body rule the mind, or does the mind| :| Mountain View, CA | rule the body? I dunno..." - Morrissey | :+-----------------------------+----------------------------------------------+ Try talking to your local NCR Comten representative for solutions to SNA and non-SNA networking problems. NCR Comten manufactures IBM plug compatible SNA front ends offering both channel and SDLC link attached connectivity. NCR Comten also has a wide ranging offering of connectivity products for non-SNA networks, connecting to both BSC and X.25 hosts. NCR Comten will shortly be offering a TCP-IP product. Initial link connectivity will be via X.25, but an Ethernet interface will also be provided. Your NCR Comten representative should be able to provide you with availability dates. -- Dan Mercer Reply-To: mercer@ncrcce.StPaul.NCR.COM (Dan Mercer)
mercer@ncrcce.UUCP (Dan Mercer) (09/28/89)
In article <8909261335.AA08004@jade.berkeley.edu> Phil Fernandez <metaphor!xymox!philf@APPLE.COM> writes: :In article <8909250654.AA16455@jade.berkeley.edu> Robert Young writes: :>I have a Sequent system (S81) connected to our 4381 mainframe through :>SNA. We have already purchased the TCP/IP tapes from IBM but are waiting :>for a hardware solution to connect the two systems. Initially, someone in :>technical marketing (IBM) suggested we use an RT and a token-ring to :>ethernet router but the idea never cooked. Now they are suggesting some :>type of channel attached device (Ethernet) to connect the two systems. :>Any ideas, suggestions and/or comments? : :IBM sells a box called the 8232, which is an industrially-packaged :PC/AT with one or more net interface boards (Ethernet and/or Token Ring) :plus one ore more channel interface boards. It is their current :standard offering for host-attach to Ethernet, and is fully supported :by the mainframe-based TCP/IP software. I had some experience with :this box when I used to work at Stanford; for the most part it works :pretty well. With the 8232, you can just put the 4381 onto your :Ethernet in just the same way you'd attach any other workstation or :mini. : :>So far it looks like the IBM people we deal with are not completely sure :>about any clear solutions. : :I can't resist a little bit of IBM-bashing in this case. The IBM :sales and systems engineering force is just not up-to-speed on the :TCP/IP and Ethernet product offerings for VM or MVS. When I was :working at Stanford, IBM was trying to sell us TCP/IP software for a :3090 running MVS. They kept trotting in more senior "experts," up to :the level of a "Regional Networking Specialist." Each of them spouted :so much silly or plain false nonsense about TCP/IP that I could barely :sit through the meetings. : :This lack of marketing commitment would really scare me about becoming :too depending on an IBM TCP/IP solution for a S/370 system. : :(This are purely my own opinions, and do not reflect those of my employer) : : :+-----------------------------+----------------------------------------------+ :| Phil Fernandez | philf@metaphor.com | :| | ...!{apple|decwrl}!metaphor!philf | :| Metaphor Computer Systems |"Does the body rule the mind, or does the mind| :| Mountain View, CA | rule the body? I dunno..." - Morrissey | :+-----------------------------+----------------------------------------------+ Try talking to your local NCR Comten representative for solutions to SNA and non-SNA networking problems. NCR Comten manufactures IBM plug compatible SNA front ends offering both channel and SDLC link attached connectivity. NCR Comten also has a wide ranging offering of connectivity products for non-SNA networks, connecting to both BSC and X.25 hosts. NCR Comten will shortly be offering a TCP-IP product. Initial link connectivity will be via X.25, but an Ethernet interface will also be provided. Your NCR Comten representative should be able to provide you with availability dates. -- Dan Mercer Reply-To: mercer@ncrcce.StPaul.NCR.COM (Dan Mercer)
drake@ibmarc.uucp (Sam Drake) (10/05/89)
The PRPQ that allows you to run TCP/IP over SNA LU 6.2 on AIX/RT is known as PRPQ number P91030. I haven't used it, and so I feel somewhat uncomfortable telling you whether it can be used in your environment or not. Suggest that you ask your SE or marketing rep to look into it. Good luck, ...Sam Drake / IBM Almaden Research Center (standard disclaimers apply) Sam Drake / IBM Almaden Research Center
drake@ibmarc.UUCP (Sam Drake) (10/05/89)
The PRPQ that allows you to run TCP/IP over SNA LU 6.2 on AIX/RT is known as PRPQ number P91030. I haven't used it, and so I feel somewhat uncomfortable telling you whether it can be used in your environment or not. Suggest that you ask your SE or marketing rep to look into it. Good luck, ...Sam Drake / IBM Almaden Research Center (standard disclaimers apply) Sam Drake / IBM Almaden Research Center