As mentioned off-list, good questions which I've passed on to the application owners. Had I my druthers there would be no TR in the picture. The Alphas are out of bounds it seems but maybe that will change.
best regards, Peter On Wed, 26 Jul 2017 10:45:02 +0800, Timothy Sipples <[email protected]> wrote: >Peter Bishop wrote: >>We're stuck with TR. > >Let's separate this out into two parts which really aren't related: >physical connectivity and protocols. > >1. For physical connectivity, why Token-Ring? Even ancient DEC AlphaServers >have/had Ethernet ports practically always. Try that path if it's >physically available. > >Also, I'm not sure why you necessarily have to connect to the IBM z13 via >FICON, although that is an option. The IBM z13 also supports Ethernet, down >as low as 100BASE-T (100 Mbps Ethernet). I'd recommend configuring at least >1000BASE-T to your switch if you can manage it since IBM has a Statement of >Direction that the IBM z14 will be the last server to support 100 Mbps >Ethernet. > >If Token-Ring is really a firm requirement, there are probably two basic >options (to Ethernet): > >(a) A Token-Ring to Ethernet bridge that supports the desired SNA protocol >(s). For example, you can still find New Old Stock IBM 8229-002s readily >available, and they're quite affordable (circa $200 it looks like). The >8229 was introduced in 1994 and withdrawn in 1998. If you choose that >option, grab an extra one. Be sure it's the -002, or equivalent, without >missing parts (i.e. with one Token-Ring module and one Ethernet module, >which were Feature Codes 4762 and 4764). > >ftp://ftp.software.ibm.com/networking/nswww/did/f1ba1000.pdf >ftp://ftp.software.ibm.com/networking/nswww/neteam/int_br.pdf >ftp://ftp.software.ibm.com/networking/nswww/neteam/netcatpr.pdf > >The IBM part number for Feature Code 4762 is 73G4762. Feature Code 4763 >(part number 73G4763) is an acceptable substitute for 4762 (dual port >Token-Ring instead of single port). The IBM part number for Feature Code >4764 is 73G4764. > >The IBM 8229 supports only 10BASE-T Ethernet, fortunately with a standard >RJ-45 connector and cable, so be sure you have a port available on your >Ethernet switch that still supports 10 Mbps Ethernet. You cannot directly >cable the IBM 8229 to an OSA port on the IBM z13. On the Token-Ring side >you will still need a little bit of Token-Ring infrastructure to pair the >AlphaServer with an IBM 8229 since Token-Ring never really had the concept >of a crossover cable. The IBM 8226 should be a good choice (if you're not >using one already), and circa $75 it looks like, but you must have >something in this role already that should work. > >(b) A bridge that you assemble that supports the desired protocol(s), for >example a PC equipped with a Token-Ring adapter and a 1000BASE-T Ethernet >port that is running IBM Communications Server: > >http://www.ibm.com/software/products/en/commserver > >2. In terms of protocols, what SNA protocol(s) is the AlphaServer using to >communicate? That's very important to figure out! The present "Rube >Goldberg" physical connectivity only gives you partial clues. It's >incredibly common for some attached device/server to be fully capable of >communicating directly -- and has been fully capable for 20+ years -- but >nobody knew that, and perhaps one or more vendors didn't reveal the >"secret." > >If you happen to know whether this AlphaServer is running Tru64 UNIX or >OpenVMS, and what SNA-related software it's running, that'd be helpful. My >preliminary investigations suggest that all the SNA software for these >operating systems had/has no problem with Ethernet, but further research >should be possible with some more information. > >-------------------------------------------------------------------------------------------------------- >Timothy Sipples >IT Architect Executive, Industry Solutions, IBM z Systems, AP/GCG/MEA >-------------------------------------------------------------------------------------------------------- > >E-Mail: [email protected] > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
