Dean If you want to know when a particular function was withdrawn, you can do worse than scanning the IBM publications pages starting here:
http://www-03.ibm.com/systems/z/os/zos/bkserv/ That is what I have just done on your behalf and I (re)confirmed that the AnyNet functions were removed in z/OS Communications Server 1.8. Here is the only significant hit when searching for "anynet" in the SNA component Network Implementation Guide: <quote> Deleted information ... AnyNet® function is removed from the z/OS V1R8 Communications Server product, and therefore documentation describing this support has been deleted. </quote> >From the way you have stated your concern, I detect that you may need some help understanding just exactly what "AnyNet" means. AnyNet products or functions within products are implementations of the MultiProtocol Transport Networking (MPTN) architecture. The objective of the architecture is to define how applications belonging to one communications protocol suite can communicate with one another using the transport functions of another communications protocol suite. There were - maybe still are - many AnyNet products which implemented the MPTN concept using pairs of communications protocol suites, one being called the A for "above" suite and the other being called the B for "below" suite. The most popular platform for the AnyNet products was the PC running OS/2 followed by the AS/400. All the IBM platforms supported two of the pairs, A=SNA, B=IP and A=IP, B=SNA. AIX/6000 and VTAM (more commonly known today as the Communications Server SNA component) supported only these two pairs. VTAM described the A=SNA, B=IP function as "AnyNet SNA over TCP/IP" and the A=IP, B=SNA function as "AnyNet Sockets over SNA". The function to which I referred in the earlier post is the latter, "AnyNet Sockets over SNA", while there is evidence that you are concerned about the former, "AnyNet SNA over TCP/IP", and, the reason for the preamble, you may not be aware of any AnyNet function other than "AnyNet SNA over TCP/IP". The evidence that you may be concerned about the "AnyNet SNA over TCP/IP" function is that you associate it with Enterprise Extender. Enterprise Extender is another way of achieving the same objective as "AnyNet SNA over TCP/IP", namely running SNA applications over the IP network. Enterprise Extender, like "AnyNet SNA over TCP/IP", presents the appearance of a logical link to the higher layers of SNA. However, whereas "AnyNet SNA over TCP/IP" presents the appearance of a logical link between type 2.1 nodes, and hence fits relatively easily into an SNA subarea network, Enterprise Extender presents the appearance of a logical link between APPN High Performance Routing (HPR) nodes which must be part of a Rapid Transport Protocol (RTP) higher level logical link. Given the recovery capabilities inherent in an RTP link, it is possible to use UDP as the transport layer for Enterprise Extender rather than TCP as in the case of the "AnyNet SNA over TCP/IP" logical link. Because of the required environment for the use of Enterprise Extender, you can no longer operate your VTAM network as a subarea network. You must introduce some fundamental changes to your VTAM network in order to enable APPN capability. This is all utterly to demolish the idea that Enterprise Extended is a "rebranding" of "AnyNet SNA over TCP/IP". It most definitely is not. I have no idea what "Va-Gen" or "Rational Business Developer" are so be aware that none of what I have said takes any account of any relevance these products might have to the topic under discussion. The other point I can make is that, like so much in SNA networking if not in IP networking, there is well-defined layering so that it would be unthinkable to imagine that changes to transport functions could be targeted to any one particular application. That "AnyNet Sockets over SNA" could be a function applying only to AFTP is a very odd suggestion! Of course you now know that it logically has no relationship whatsoever with "AnyNet Sockets over SNA"; "AnyNet Sockets over SNA" refers to FTP. I hope that's enough of a clarification for you. If not, please post again. Chris Mason ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
