Thanks Tom. I agree Hiper Sockets would be my first choice, but I was told it would not be configured for this machine. Since I can use CTC, I will use that for now until the Network team can investigate the issue with the switch.
-----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Tom Longfellow Sent: Tuesday, October 3, 2023 6:18 AM To: [email protected] Subject: Re: SNA Link Replacement in Z/OS 2.5 Timothy has been very clear on some options for you. I may be making invalid assumptions here by reading between the lines of your post. If you are using DEVICE and LINK statements they really need to be converted to INTERFACE statements. Most of the enhancements tor IP over the last several years has been implemented ONLY for the INTERFACE. There are TCPIP commands that can help you do the conversion. I have used all of the different paths that Timothy mentioned. VTAM automatically joins the XCF network of LPARS for SNA purposes. I usually inactivate it to cut down on Path Switching between competing ways to get between A and B. Hipersockets is my Backbone between LPARs on the same box. I have my own private network that runs the SNA VIPA addresses without ever leaving the I/O subsystem. The SMC-D add on was a nice bonus but we have such low usage rates that it is hard to find the differences. CTC was my day one method when I first implemented APPN networking many years ago. But, if you can not get them to implement Hipersockets, then CTC is just as unavailable to you. Overall Hipersockets outperforms CTC hands down. CTC does outperform XCF. If the majority of your traffic is between LPARs in the same IP Segment, A Shared OSA is the way to go. Why bother with the Network Switch if you do not have to. The OSA is both your interface AND your network switch. This may also generate some hardware configuration changes to make the OSA available to all of the sister LPARS. I was never able to get SNALINK definitions to work for me. And now I have a surplus of Other ways to get the job done. ---------------------------------------------------------------------- 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
