Chris, sorry to be so ambiguous. What I'm trying to do is get rid of some old IBM equipment at remote locations. It is being replaced by Windows Communications Server and LANDP. The reason I ask about SNA Gateway, etc.. is that in configuring the Windows Comm Server the Wizard has a dropdown window that has various configurations that you can choose from. I.E.
SNA GATEWAY APPN Network Node DLUR/DLUS Support for Local LU's DLUR/DLUS Support for Downstream LU's AnyNet SNA over TCP/IP Gateway AnyNet Sockets over SNA SNA API Clients Running APPC Applications SNA API Clients Running 3270 or other LUA Applications 3270/LUA Applications Focal Point AS/400 Shared Folders Some of these I have heard about, others I didn't even know they existed. Either way once windows comm server is set up and talking to the mainframe the desktops at the remote location will talk to the Comm server and send info back and forth to mainframe via the comm Server. In order to minimize the impact of installation, I have been designated to set up communications to this windows server and make it communicate with the mainframe CICS system. The LU names currently in use must not change. In other words. If you had a 3174 remote with LU A,B,C you would need to set up Windows Comm Server in some fashion that would allow it to have LU A,B,C connect to CICS just like the 3174 remote did. I am confused because I have never had to set up SNA communications with a software server. It's always been SNA to another VTAM using a 3745, 3705 and NCP, or to a remote 32xx device. I think the HPR APPN node is the way to go since it offers the most current mode of communications, but I may be all wet. That's why I'm asking so many questions. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Chris Mason Sent: Wednesday, July 08, 2009 8:03 PM To: [email protected] Subject: Re: Anynet Mike I was composing this response before your posts appeared on the IBMTCP-L list. > ... is anynet incorporated into z/os vtam like enterprise extender is? Two of the AnyNet components, "SNA over IP"[1] and "Sockets over SNA", *used* to be "incorporated" into VTAM (the Communications Server SNA component) prior to V1R8 - and unchanged since V1R2 - in the sense that you did not have to obtain a separate product in order to acquire the function.[2] Note that simply saying AnyNet is ambiguous. The fact that you are also interested in Enterprise Extender indicates that it is AnyNet SNA over IP in which you are interested. The other AnyNet implementation which used to be supported by VTAM is AnyNet Sockets over SNA which was withdrawn at the same time as AnyNet SNA over IP and for which there is - a pause for a tear - no replacement. AnyNet products are implementations of the Multiprotocol Transport Networking (MPTN) principle and there used to be quite a number where one protocol suite switched to another protocol suite in principle at the level of the transport layer of the ISO OSI model. Note that MPTN actually incorporates some RFCs. I suppose AnyNet SNA over IP is "just like enterprise extender" since the VBUILD TYPE=TCP is available in the same way as the VBUILD TYPE=XCA followed by PORT MEDIUM=HPRIP can be coded in a VTAM major node definition. There is a difference in that the AnyNet components were always described in separate manuals. See http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/F1A1BK61 You seem to imply that z/OS V1R7 is your current level. This being so, you could have answered your first question from your installed VTAM. Like Pat, I am somewhat puzzled by your terminology. You seem to have the idea that the distributed platforms are tied to z/OS in some manner other than that they both implement SNA. It is as if SNA were somehow a feature of z/OS that gets exported to distributed platforms in some way. I hope the IBM "suits'" insistence back in about 1995 that "if it's SNA, whatever the platform, it has to be a member of the 'Communications Server' family" hasn't confused you appreciation of the technical truth. The "Communications Server" family label makes some sort of technical sense for all the products so labeled ***with the very specific exception of the z/OS one*** because the same software house was and is still I believe responsible for them. See http://www-01.ibm.com/software/network/commserver/library/ and try to ignore the "Communications Server for zOS and CS390" entry! You also rather mistakenly emphasise the word "gateway". I expect by "gateway" you refer to the optional and, to my mind, generally unnecessary technique of having either LU type 2 (3270) or LU type 6.2 (APPC) data streams passed over a typically local IP network to the workstations rather than extending SNA to the workstations and using an APN Network Node server or a Branch Extender Node[3]. Why mix your protocols when you don't have to? I guess this is all related to the other thread to which I have given you some responses. Much as Timothy Sipples suggested, you should just say what you ***really*** want to do - without "prejudice". Chris Mason [1] I always drop the "TCP" because, in fact, "AnyNet over IP" also uses UDP port 397 (by default). [2] FWIW I even remember that the CM/2 support for the two AnyNet components was shipped with VTAM when the function first became available. [3] Your only option when you try to build an SNA network on "one-size-fits- all" Cisco SNASw. On Tue, 7 Jul 2009 16:03:10 -0500, Ward, Mike S <[email protected]> wrote: >Hello all, is anynet incorporated into z/os vtam like enterprise >extender is? Or is there any way to communicate with an SNA >Gateway(Communications Server) from z/os 1.7 using the enterprise >extender functions? > >Thanks. ---------------------------------------------------------------------- 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 ========================== This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. ---------------------------------------------------------------------- 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
