IP Services: Modify GLOBALCONFIG SMCR PFID definitions
Description
In z/OS V2R1 Communications Server, VTAM provided physical function services for IBM 10GbE RoCE Express features used for Shared Memory Communications via Remote Direct Memory Access (SMC-R) processing. This allowed multiple TCP/IP stacks operating in the same logical partition (LPAR) to share a RoCE Express feature by configuring and activating the same Peripheral Component Interconnect Express (PCIe) function ID (PFID) representation of the feature. Starting with z/OS V2R2 on a z13 server, each TCP/IP stack must have unique PFID values to represent the RoCE Express feature.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
Element or feature: | z/OS Communications Server. |
---|---|
When change was introduced: | z/OS V2R2. |
Applies to migration from: | z/OS V2R1. |
Timing: | Before the first IPL of z/OS V2R2. |
Is the migration action required? | Yes, if all the following conditions are true:
|
Target system hardware requirements: | Only applicable to a z13 server. If you are running on a server before z13, this migration action does not apply to you. |
Target system software requirements: | None. |
Other system (coexistence or fallback) requirements: | None. |
Restrictions: | None. |
System impacts: | None. |
Related IBM® Health Checker for z/OS® check: | None. |
Steps to take
- Use the hardware configuration definition (HCD) to define a unique FID value for each TCP/IP stack that will be activating the 10GbE RoCE Express feature. You must also assign a virtual function number (VFN) for each potential user of the 10GbE RoCE Express feature.
- Modify the GLOBALCONFIG SMCR statement in the TCP/IP profile to specify the PFID values that are assigned for this stack. Update the GLOBALCONFIG statements for all TCP/IP stacks that activate a given 10GbE RoCE Express before starting any of the TCP/IP stacks. The PFID values should correspond to the FID values you defined in the HCD.
Reference information
For more information, see z/OS Communications Server: IP Configuration Guide.