When source VIPA is in effect, you can control which static VIPA is used for your IPv4 dynamic XCF interfaces by using the new SOURCEVIPAINTERFACE parameter on IPCONFIG DYNAMICXCF in z/OS V2R1. This designation removes the need to manage the order of the VIPAs in the HOME list. For the syntax of this new parameter, see the V2R1 IP Configuration Reference.
z/OS Communications Server
SamReynolds 270004DVAN 5,145 Views
z/OS V2R1 supports IPv4 INTERFACE definitions for HiperSockets and Static VIPA in addition to the prior support for OSA-Express QDIO. The IPv4 INTERFACE statement combines the function of DEVICE/LINK/HOME into a single statement. This simplifies your stack configuration and also improves the usability of dynamically adding or removing these interfaces from your TCP/IP profile (which can be cumbersome when the HOME statement is involved). If you use the source VIPA function, the INTERFACE statement makes it much easier to designate which VIPA to use for the source IP address (without needing to manage the order of VIPAs in the HOME list). For the syntax of these statements, see the V2R1 IP Configuration Reference.
SamReynolds 270004DVAN 5,016 Views
On October 9th, z/OS Communications Server held a Twitter chat with a focus on z/OS V2R1 CS features. Below is a transcript of that chat (with minor edits for clarification).
Welcome to our Twitter chat on z/OS V2R1 CS! Tweet your V2R1 CS questions with the hashtag #zoscs21
Q1: Is the default for SOMAXCONN sufficient for 250,000 Telnet TN3270E sessions? #zoscs21
A1: In V2R1, we've raised the SOMAXCONN default from 10 to 1024. That should be sufficient for that TN3270 workload. #zoscs21
V2R1 Fact: V2R1 introduces support for RDMA, with up to an 80% reduction in latency. For more information, see: https://t.co/F6tatQuoAe #zoscs21
Q2: Any plans to have ACF/TAP analyze IP packet traces? #zoscs21
A2: We have no plans for any updates to ACF/TAP. #zoscs21
V2R1 Fact: In addition to RDMA, V2R1 supports many other new features. For an overview, see this screencast: http://t.co/MBt0y4AnqT #zoscs21
Q3: Not a CommServer question but mainframe network - will WLM ever be able to loadbalance geographically dispersed SYSPLEXs? #zoscs21
A3, Part 1: WLM can provide load balancing advice for a single sysplex even if it is geographically dispersed #zoscs21
A3, Part 2: With IBM's GDPS Active-Active solution, load balancing can span different sysplexes using ... #zoscs21
A3, Part 3: ... the IBM Multi-Site Workload Lifeline product and an external load balancer. #zoscs21
V2R1 Fact: No longer have to say "Oops!" With V2R1, you can check the syntax of a TCP/IP Profile prior to activating it. #zoscs21
That's it for today's #zoscs21 chat! Thanks for your participation!