## D.2.10 Enabling SMC-R support in z/OS Communications Server 

The following checklist provides a task summary for enabling SMC-R support in z/OS Communications Server. This list assumes that you start with an IP configuration for LAN access that uses OSD: 

 HCD definitions (install and configure RNICs in the HCD): 

 Add the PNet ID for the current OSD. 

 Define PFIDs for RoCE (with the same PNet ID). 

 Specify the GLOBALCONFIG SMCR  parameter (TCP/IP Profile): 

 Must specify at least one PCIe Function ID (PFID): 

 A PFID represents a specific RNIC adapter. 

 A maximum of 16 PFID values can be coded. 

 Up to eight TCP/IP stacks can share a RoCE PCHID (RoCE adapter) in a specific LPAR (each stack must define a unique FID value). 

 Start the IPAQENET or IPAQENET6 INTERFACE with CHPIDTYPE OSD: 

 SMC-R is enabled, by default, for these interface types. 

 SMC-R is not supported on any other interface types. 

Note:  The IPv4 INTERFACE statement (IPAQENET) must also specify an IP subnet mask 

 Repeat in each host (at least two hosts). 

Start the TCP/IP traffic and monitor it with Netstat and IBM VTAM displays. 

Note:  For RoCE Express2, the PCI Function IDs (PFIDs) are now associated with a specific (single) physical port (that is, port 0 or port 1). The port number is now configured with the FID number in HCD (or IOCDS) and the port number must be configured (no default is available). z/OS CommServer does not learn the RoCE generation until activation. During activation, CommServer learns the port number for RoCE Express2. 

Consider the following points: 

GLYPH<SM590000> The port number for RoCE Express is configured in z/OS TCP/IP profile and does not change. 

GLYPH<SM590000> When defining a FID in the TCP/IP profile for RoCE Express2, the port number is no longer applicable (it is ignored for RoCE Express2). 

GLYPH<SM590000> A warning message is issued if the TCP/IP profile does not match the HCD configured value (that is, the value is ignored and it is incorrect). 

