HiperSockets IOCP definitions on z14 ZR1:  A parameter was added for HiperSockets  IOCP definitions on z14 ZR1, z14 M0x, z13, and z13s servers. Therefore, the IOCP  definitions must be migrated to support the HiperSockets definitions (CHPID type IQD).  On z14 ZR1, z14 M0x, z13, and z13s servers, the CHPID statement of HiperSockets  devices require the keyword VCHID. VCHID specifies the virtual channel identification  number that is associated with the channel path. The vSalid range is 7E0 - 7FF.  VCHID is not valid on Z servers before z13. For more information, see  IBM Z Input/Output Configuration Program User's Guide for ICP  IOCP,  SB10- 7172. HiperSockets can be customized to accommodate varying traffic sizes. Because  HiperSockets does not use an external network, it can free up system and network resources.  This advantage can help eliminate attachment costs and improve availability and  performance. HiperSockets eliminates the need to use I/O subsystem operations and traverse an external  network connection to communicate between LPARs in the same z14 ZR1 server.  HiperSockets offers significant value in server consolidation when connecting many virtual  servers. It can be used instead of certain coupling link configurations in a Parallel Sysplex. HiperSockets internal networks support the following transport modes:  Traffic can be IPv4 or IPv6, or non-IP, such as AppleTalk, DECnet, IPX, NetBIOS, or SNA. HiperSockets devices are protocol-independent and Layer 3-independent. Each  HiperSockets device (Layer 2 and Layer 3 mode) features its own Media Access Control  (MAC) address. This address allows the use of applications that depend on the existence of  Layer 2 addresses, such as Dynamic Host Configuration Protocol (DHCP) servers and  firewalls.  Layer 2 support helps facilitate server consolidation, and can reduce complexity and simplify  network configuration. It also allows LAN administrators to maintain the mainframe network  environment similarly to non-mainframe environments. Packet forwarding decisions are based on Layer 2 information instead of Layer 3. The  HiperSockets device can run automatic MAC address generation to create uniqueness within  and across LPARs and servers. The use of Group MAC addresses for multicast is supported,  and broadcasts to all other Layer 2 devices on the same HiperSockets networks. Datagrams are delivered only between HiperSockets devices that use the same transport  mode. A Layer 2 device cannot communicate directly to a Layer 3 device in another LPAR  network. A HiperSockets device can filter inbound datagrams by VLAN identification, the  destination MAC address, or both. Analogous to the Layer 3 functions, HiperSockets Layer 2 devices can be configured as  primary or secondary connectors, or multicast routers. This configuration enables the creation  of high-performance and high-availability link layer switches between the internal  HiperSockets network and an external Ethernet network. It also can be used to connect to the  HiperSockets Layer 2 networks of different servers. GLYPH<SM590000> Layer 2 (link layer) GLYPH<SM590000> Layer 3 (network or IP layer) 152  IBM 14 Model ZR1 Technical Guide