Re: IBM-MAIN Digest - 19 Sep 2010 to 20 Sep 2010 (#2010-263)
There is another one, i an ware of Anynetwhether it is used any more, I dont know. Scott J Ford From: David Boyes dbo...@sinenomine.net To: IBM-MAIN@bama.ua.edu Sent: Tue, September 21, 2010 12:36:06 AM Subject: Re: IBM-MAIN Digest - 19 Sep 2010 to 20 Sep 2010 (#2010-263) No real issue, just thought I would ask. I couldn't think of anything other than an OSA for TCP/IP communication. I had forgotten about the CIPS from CISCO. There are a fair number of devices that work with IBM TCPIP (both for VM and for MVS). Some other fun ones: 7170 (basically a parallel channel interface to a DEC Unibus card cage, with a DEC DELNI network card in it, controlled by an original IBM PC with (wait for it!) 64K of RAM!), Genned as a CTC. Very temperamental, but it got bits on the wire. 8232 (a channel attached PC/AT that came with a Ungermann/Bass 10mbit Ethernet card that jammed easily on networks with lots of collisions) also genned as a CTC 3172 (aka LAN Channel Station, or LCS) genned as 3088, could support up to 3 network adapters (TR, Ethernet, ATM), although you were sad if you had the ATM adapter and tried to add anything else to it). This is the most common emulated adapter, and was available internally on the MP3K, FlexES and now zPDT. Came in parallel and ESCON versions, I think. BusTech BTI 1, 2 and 3: very popular with universities, as they were about a quarter to half the price of a 8232 or 3172 and took up a LOT less space (4 RU vs a half-height cabinet for a 3172). V1 required a special driver, but later models emulated a 3088. Supported Ethernet, TR, and ATM in various forms, and you could get one unit to support up to 4 adapters (the vendor sold only 3, but there was plenty horsepower for 10 Mbit Ethernet. ATI Hyperchannel -- did 10 and 100mbit Ethernet direct from the channel interface. Expensive, usually used when you had a Cray to do computing and the Z system was just playing smart I/O device to the Cray. X25IPI -- IP over X.25. You needed a FEP for this thing, or the internal X.25 interface in a 4361. Evil. Pure Evil. SNA LU - IP over SNA. VTAM set up a LU-LU session, and the IP stack used it like a serial line. Weird, but it worked. Cisco CIP - channel attached 75xx Cisco router. Parallel and ESCON versions, genned as a 3088. Fast (for the day) and very flexible. Could drive dozens of interfaces, offload 3270 traffic, deal with up to SONET speeds, bridge Ethernet and TR and ATM networks. The channel interface was the real bottleneck. Too bad there never was a FICON version. Cisco CPA - channel attached 72xx Cisco router. Similar to a CIP, but designed for the smaller 7200 series routers. Also had a parallel and ESCON version. Real CTC/CNCs -- if you had a 3088, you could use it to connect to other Z hosts and do IP over the channel. Fast, for the day, but not very useful unless you were VERY visionary and fought the SNA Wars well. The lockstep nature of the channel protocol was the big bottleneck. About that point was where the OSAs appeared. The stack still has the code to support most of these devices, but IBM (and the other vendors) probably don't support them officially any more. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM-MAIN Digest - 19 Sep 2010 to 20 Sep 2010 (#2010-263)
AFAIK ANYNET is no longer supported. Replaced w/Enterprise Extender snip There is another one, i an ware of Anynetwhether it is used any more, I dont know. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
AnyNet, dead or alive? (Was: Re: IBM-MAIN Digest - 19 Sep 2010 to 20 Sep 2010 (#2010-263) - Was: z/OS, TCP/IP, and OSA)
Allan AFAIK ANYNET is no longer supported. This is one of those points that is very easy to discover from the on-line manuals - just as the original question was, come to think of it - and, more recently a probably for which the exact opposite is a certainty. I may find sufficient energy to expand on the latter later. On the following bookshelf for z/OS V1R7, we still find the AnyNet feature manuals: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/F1A1BK61 On the following bookshelf for z/OS V1R8, we find they have mysteriously disappeared: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/F1A1BK81 Well, it's not *so* mysterious when we take the trouble to dip into the so- called z/OS Communications Server New Function Summary, Version 1 Release 8, GC31-8771-02, manual, we find the following (new function indeed!): quote | 2.2.2.1 Current support considerations ... | z/OS V1R8 Communications Server discontinues support of AnyNet®. | AnyNet consists of two functions: SNA over IP, and Sockets over SNA. | You can implement Enterprise Extender (EE) as the replacement for the | SNA over IP function. There is no replacement for Sockets over SNA. /quote Replaced w/Enterprise Extender Yes and no as you can see above if you read it all. Of course, if you rely on the following piece of mendacity, you will fall into the trap of imagining that AnyNet has been replaced in full: quote 2.3.1.2 Future support considerations Be aware of the following future support considerations and refer to z/OS Migration for information about migration. z/OS V1R7 Communications Server is planned to be the last release to support AnyNet. After z/OS V1R7, the function will be removed from the product. You can implement Enterprise Extender (EE) as the replacement for AnyNet. /quote The manual authors do not seem to be able to read what they themselves have written within the scope of one manual here. Definitely a double-bogey! There is another one, i an ware of Anynetwhether it is used any more, I dont know. Which, being translated, is probably intended to say the following: There is another one (means of supplying an IP interface to z/OS Communications Server) of which I am aware: AnyNet. Whether or not it is used any more, I don't know. Actually, what may have been in mind is that flavour of subset of AnyNet products - which extend(ed) to many platforms, not just MVS - which everyone - except the person exercising his fingertips at the moment! - tends to overlook, namely the brilliant AnyNet Sockets over SNA which allows a superb IP application - not actually the IP kernel - to use the superb SNA network for transport rather than the ramshackle IP network. This is the inherent characteristic of the Multiprotocol *Transport* Networking (MPTN) architecture of which the AnyNet products, not limited to the z/OS platform, are implementations. So, in the last analysis, it's interesting to mention AnyNet and, by implication, MPTN, but no flavour of AnyNet is actually an implementation of an IP interface. Chris Mason On Tue, 21 Sep 2010 12:14:41 -0500, Staller, Allan allan.stal...@kbm1.com wrote: AFAIK ANYNET is no longer supported. Replaced w/Enterprise Extender snip There is another one, i an ware of Anynetwhether it is used any more, I dont know. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM-MAIN Digest - 19 Sep 2010 to 20 Sep 2010 (#2010-263)
No real issue, just thought I would ask. I couldn't think of anything other than an OSA for TCP/IP communication. I had forgotten about the CIPS from CISCO. There are a fair number of devices that work with IBM TCPIP (both for VM and for MVS). Some other fun ones: 7170(basically a parallel channel interface to a DEC Unibus card cage, with a DEC DELNI network card in it, controlled by an original IBM PC with (wait for it!) 64K of RAM!), Genned as a CTC. Very temperamental, but it got bits on the wire. 8232(a channel attached PC/AT that came with a Ungermann/Bass 10mbit Ethernet card that jammed easily on networks with lots of collisions) also genned as a CTC 3172(aka LAN Channel Station, or LCS) genned as 3088, could support up to 3 network adapters (TR, Ethernet, ATM), although you were sad if you had the ATM adapter and tried to add anything else to it). This is the most common emulated adapter, and was available internally on the MP3K, FlexES and now zPDT. Came in parallel and ESCON versions, I think. BusTech BTI 1, 2 and 3: very popular with universities, as they were about a quarter to half the price of a 8232 or 3172 and took up a LOT less space (4 RU vs a half-height cabinet for a 3172). V1 required a special driver, but later models emulated a 3088. Supported Ethernet, TR, and ATM in various forms, and you could get one unit to support up to 4 adapters (the vendor sold only 3, but there was plenty horsepower for 10 Mbit Ethernet. ATI Hyperchannel -- did 10 and 100mbit Ethernet direct from the channel interface. Expensive, usually used when you had a Cray to do computing and the Z system was just playing smart I/O device to the Cray. X25IPI -- IP over X.25. You needed a FEP for this thing, or the internal X.25 interface in a 4361. Evil. Pure Evil. SNA LU - IP over SNA. VTAM set up a LU-LU session, and the IP stack used it like a serial line. Weird, but it worked. Cisco CIP - channel attached 75xx Cisco router. Parallel and ESCON versions, genned as a 3088. Fast (for the day) and very flexible. Could drive dozens of interfaces, offload 3270 traffic, deal with up to SONET speeds, bridge Ethernet and TR and ATM networks. The channel interface was the real bottleneck. Too bad there never was a FICON version. Cisco CPA - channel attached 72xx Cisco router. Similar to a CIP, but designed for the smaller 7200 series routers. Also had a parallel and ESCON version. Real CTC/CNCs -- if you had a 3088, you could use it to connect to other Z hosts and do IP over the channel. Fast, for the day, but not very useful unless you were VERY visionary and fought the SNA Wars well. The lockstep nature of the channel protocol was the big bottleneck. About that point was where the OSAs appeared. The stack still has the code to support most of these devices, but IBM (and the other vendors) probably don't support them officially any more. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
