Only minor changes are required for z/VM guests. An OS can be enabled for SMC-R and  SMC-D. SMC-D is used when both peers are within the same CPC (and ISM PNet and  VLAN). After the ISM HCD configuration is complete, SMC-D can be enabled in z/OS with a  single TCP/IP parameter (GLOBALCONFIG SMCD). ISM FIDs must be associated with an IP  network. The association is accomplished by matching PNet IDs (for example, HiperSockets  and ISM).  Note:  ISM FIDs must be associated with HiperSockets or with an OSA adapter by using a  PNet ID. It cannot be associated to both. SMC-D over ISM features the following prerequisites: The required APARs per z/OS subsystem are listed in Table D-1. D.3.10 SMC-D over ISM prerequisites GLYPH<SM590000> IBM z14, z13s, or z13 (Driver 27): HMC/SE for ISM vPCI Functions. GLYPH<SM590000> At least two z/OS V2.2 systems (or later) in two LPARs on the same CPC with required  service installed: – SMC-D can communicate with another z/OS V2.2 instance only and peer hosts must  be on the same CPC and ISM PNet. – SMC-D requires an IP Network with access through OSA or HiperSockets that includes  a defined PNet ID that matches the ISM PNet ID. GLYPH<SM590000> If running as a z/OS guest under z/VM, z/VM 6.3 with APAR VM65716, including APARs is  required for guest access to RoCE (Guest Exploitation only). GLYPH<SM590000> Linux support is planned for a future deliverable. Subsystem FMID APAR IOS HBB77A0 OA47913 Communications Server SNA  VTAM HVT6220 OA48411 Communications Server IP HIP6220 PI45028 HCD HCS77A0 HCS7790 HCS7780 HCS7770 HCS7760 HCS7750 OA46010 IOCP HIO1104 OA47938 HCM HCM1F10 HCM1E10 HCM1D10 HCM1C10 HCM1B10 HCM1A10 IO23612 Table D-1 Prerequisite APARs for SMC-D enablement Appendix D. Shared Memory Communications  447