PROFILE.TCPIP statement and parameter changes

Table 1 lists the new and updated Communications Server PROFILE.TCPIP configuration statements and parameters. See z/OS Communications Server: IP Configuration Reference for more detailed information.

Table 1. Summary of new and changed Communications Server PROFILE.TCPIP configuration statements and parameters
Statement Release Description Reason for change
ATMARPSV, ATMLIS, ATMPVC V2R2 Support for these profile statements is removed because the ATM device type is no longer supported. Removal of support for legacy devices
V2R1 Because support for the ATM device type will be dropped in a future release, these profile statements will no longer be supported then. IBM Health Checker for legacy device types
AUTOLOG V2R1 Message EZZ0621I or EZZ0622I will be issued on the first cancel of an autologged procedure. Release update

DELETE PORT
DELETE PORTRANGE

 V2R1 For TCP ports, if no reservation is found for the port or the reservation was deleted in the current profile processing, error message EZZ0328I is issued instead of message EZZ0395I. Message EZZ0395I will continue to be issued for other errors. Update your message automation for this change. Release update
DEVICE V2R2 The following DEVICE types and their corresponding LINK profile statements are no longer supported:
  • ATM
  • CDLC
  • CLAW
  • HYPERchannel
  • SNALINK (LU0 and LU6.2)
  • X.25
 Removal of support for legacy devices
Start of changeDEVICE and LINKEnd of change Start of changeV2R2End of change Start of changeSupport for the DEVICE and LINK profile statements for the following TCP/IP legacy device types will be dropped in a future release:
  • FDDI and Token Ring (LCS with LINKs FDDI and IBMTR)
  • Token Ring (MPCIPA with LINK IPAQTR)
  • Ethernet and FDDI (MPCOSA with LINKs OSAENET and OSAFDDI)
End of change		 Start of changeIBM Health Checker for additional z/OS legacy device typesEnd of change
V2R1 Support for the DEVICE and LINK profile statements for the following TCP/IP legacy device types will be dropped in a future release:
  • ATM
  • CDLC
  • CLAW
  • HYPERchannel
  • SNALINK (LU0 and LU6.2)
  • X.25
 IBM Health Checker for legacy device types
GATEWAY V2R2 Support for this profile statement is removed. The BEGINROUTES statement can be used to configure static routes. Removed support for the GATEWAY statement in the TCP/IP profile
V2R1 Support for this profile statement will be dropped in a future release. Use the BEGINROUTES/ENDROUTES configuration block to replace your GATEWAY statements. To assist in converting your GATEWAY statements to BEGINROUTES statements, you can take a dump of the TCP/IP stack address space and use the CONVERT parameter on the IPCS TCPIPCS PROFILE subcommand. The TCPIPCS command output will contain the information that is specified on the GATEWAY statements converted to the equivalent BEGINROUTES/ENDROUTES statements. See "TCPIPCS PROFILE" in the IP Diagnosis Guide for more information. IBM Health Checker for z/OS GATEWAY statement check
Start of changeGLOBALCONFIG End of change Start of changeV2R2End of change Start of changeThe SMCD parameter is defined to enable and configure the Shared Memory Communications - Direct Memory Access (SMC-D) function. The SMCD parameter includes the FIXEDMEMORY and TCPKEEPMININTERVAL subparameters. The NOSMCD parameter is defined to disable SMC-D function.End of change Start of changeShared Memory Communications - Direct Memory AccessEnd of change
V2R2 The ADJUSTDVIPAMSS parameter is added to control whether TCP/IP adjusts the Maximum Segment Size for TCP connections. VIPAROUTE fragmentation avoidance
V2R2 For the SMCR parameter, a new value of 4096 can be specified for the MTU subparameter. Shared Memory Communications over RDMA enhancements
Start of changeV2R2End of change Start of changeAdded SMCGLOBAL parameter to provide global settings for the Shared Memory Communications over Remote Direct Memory Access (SMC-R) function and Shared Memory Communications - Direct Memory Access (SMC-D) function. The following subparameters can be specified:
  • AUTOCACHE and NOAUTCACHE

    Control caching of unsuccessful attempts to use SMC-R or SMC-D.

  • AUTOSMC and NOAUTOSMC

    Control monitoring incoming TCP connections to determine whether they would benefit from SMC-R or SMC-D.

End of change		 Start of change
  • Shared Memory Communications over RDMA enhancements
  • Shared Memory Communications - Direct Memory Access (SMC-D)
End of change
V2R1 The PFID operand on the SMCR statement is changed to accept a range of values between X'0000' and X'0FFF'. Shared Memory Communications over RDMA adapter (RoCE) virtualization
V2R1 The SMCR parameter is defined to enable and configure Shared Memory Communications over Remote Direct Memory Access (SMC-R) function. The SMCR parameter includes the PFID, PORTNUM, MTU, FIXEDMEMORY, and TCPKEEPMININTERVAL sub-parameters. The NOSMCR parameter is defined to disable SMC-R function. Shared Memory Communications over Remote Direct Memory Access
GLOBALCONFIG V1R13 Deprecated the SEGMENTATIONOFFLOAD and NOSEGMENTATIONOFFLOAD parameters. OSA-Express4S QDIO IPv6 checksum and segmentation offload
V1R13 Added the AUTOIQDX and NOAUTOIQDX parameters. The AUTOIQDX parameter includes the ALLTRAFFIC and NOLARGEDATA sub-parameters. HiperSockets optimization for intraensemble data networks
Start of changeINTERFACEEnd of change Start of changeV2R2End of change Start of changeThe SMCD parameter is defined to enable the SMC-D function for the following statements:
  • IPAQENET, when CHPIDTYPE OSD is specified
  • IPAQENET6, when CHPIDTYPE OSD is specified
  • IPAQIDIO
  • IPAQIDIO6
The NOSMCD parameter is defined to disable the SMC-D function.End of change		 Start of changeShared Memory Communications - Direct Memory AccessEnd of change
V2R1 Can be used to configure IPv4 HiperSockets interfaces (IPAQIDIO) instead of the DEVICE, LINK, and HOME statements. IPv4 INTERFACE statement for HiperSockets and Static VIPAs
V2R1 Can be used to configure IPv4 static VIPA interfaces (VIRTUAL) instead of the DEVICE, LINK, and HOME statements. IPv4 INTERFACE statement for HiperSockets and Static VIPAs
V2R1 For IPAQENET interface types, added new TEMPIP parameter to allow an interface to activate without an IP address assigned. Applications which implement DHCP client support can communicate over the interface to obtain an IP address. Enable DHCP clients on OSA Interfaces
V2R1 The SMCR parameter is defined to enable Shared Memory Communications - RDMA (SMC-R) function for IPAQENET and IPAQENET6 statements. The SMCR parameter is valid only for CHPIDTYPE OSD definitions. The NOSMCR parameter is defined to disable SMC-R function. Shared Memory Communications over Remote Direct Memory Access
Start of changeIPCONFIGEnd of change Start of changeV2R2End of change Start of changeThe SMCD subparameter is defined on this statement for the DYNAMICXCF parameter to enable the SMC-D function. The NOSMCD subparameter is defined to disable SMC-D function.End of change Start of changeShared Memory Communications - Direct Memory AccessEnd of change
V2R2 Support for the CLAWUSEDOUBLENOP and STOPONCLAWERROR parameters is removed because the CLAW device type is no longer supported. Removal of support for legacy devices
V2R1 You can enable QDIOACCELERATOR when IPSECURITY is enabled. QDIO acceleration coexistence with IP filtering
V2R1 The SOURCEVIPAINTERFACE parameter is added for IPv4 DYNAMICXCF interfaces. IPv4 INTERFACE statement for HiperSockets and Static VIPAs
V1R13 Added CHECKSUMOFFLOAD and NOCHECKSUMOFFLOAD and SEGMENTATIONOFFLOAD and NOSEGMENTATIONOFFLOAD parameters. OSA-Express4S QDIO IPv6 checksum and segmentation offload
Start of changeIPCONFIG6End of change Start of changeV2R2End of change Start of changeThe SMCD subparameter is defined on this statement for the DYNAMICXCF parameter to enable the SMC-D function. The NOSMCD subparameter is defined to disable SMC-D function.End of change Start of changeShared Memory Communications - Direct Memory AccessEnd of change
V1R13 Added CHECKSUMOFFLOAD and NOCHECKSUMOFFLOAD and SEGMENTATIONOFFLOAD and NOSEGMENTATIONOFFLOAD parameters. OSA-Express4S QDIO IPv6 checksum and segmentation offload
V1R13 If you do not specify the IGNOREREDIRECT parameter and you are using Intrusion Detection Services (IDS) policy to detect and discard Redirect packets, ICMPv6 Redirect packets are discarded while the policy is active. Expanded Intrusion Detection Services
IPSEC V2R2 The IPSECRULE and IPSEC6RULE statements support new and modified parameters that can be used to configure enhanced default IP filter policy. TCPIP profile IP security filter enhancements
Start of changeV2R2End of change Start of changeA new parameter, DVLOCALFLTR, is added to the IPSEC statement. DVLOCALFLTR enables IP filtering of TCP traffic between a client and an IPv4 dynamic VIPA defined on the same TCP/IP stack, when the traffic is forwarded to another TCP/IP stack.End of change Start of changeAPAR PI44865End of change
Start of changeV2R1End of change Start of changeAPAR PI40291End of change
V2R1 The DVIPSEC parameter enables the support for Sysplex-Wide Security Associations (SWSA) for IPv6 on a stack that also has the IPSECURITY parameter specified on the IPCONFIG6 statement. Sysplex-Wide Security Associations for IPv6
NETACCESS V2R1 The CACHEALL, CACHEPERMIT, and CACHESAME parameters are added to control the level of caching that is used for the results of network access control checks. Improve auditing of NetAccess rules
NETMONITOR V2R1 The PROFILE and NOPROFILE subparameters control the creation of both the TCP/IP stack SMF 119 profile record (subtype 4) and the new TN3270E Telnet server SMF 119 profile record (subtype 24). NMI and SMF enhancements for TCP/IP applications
Start of changePORTEnd of change Start of changeV2R2End of change Start of change
  • The SMC parameter is enhanced to enable SMC-D function for the specified port.
  • The NOSMC parameter is enhanced to disable SMC-D function for the specified port.
End of change		 Start of changeShared Memory Communications - Direct Memory AccessEnd of change
V2R2
  • The SMC parameter is defined to enable SMC-R function for the specified port. This parameter applies only to TCP ports and is required only when AUTOSMC monitoring is in effect.
  • The NOSMCR parameter has been deprecated but will still be accepted. The NOSMC parameter is the preferred parameter to disable SMC-R function for the specified port.
 Shared Memory Communications over RDMA enhancements
V2R1 The NOSMCR parameter is defined to disable SMC-R function for the specified port. Shared Memory Communications over Remote Direct Memory Access
Start of changePORTRANGEEnd of change Start of changeV2R2 End of change Start of change
  • The SMC parameter is enhanced to enable the SMC-D function.
  • The NOSMC parameter is enhanced to disable the SMC-D function.
End of change		 Start of changeShared Memory Communications - Direct Memory AccessEnd of change
V2R2
  • The SMC parameter is defined to enable SMC-R function for the specified port. This parameter applies only to TCP ports and is required only when AUTOSMC monitoring is in effect.
  • The NOSMCR parameter has been deprecated but will still be accepted. The NOSMC parameter is the preferred parameter to disable SMC-R function for the specified port.
 Shared Memory Communications over RDMA enhancements
V2R1 The NOSMCR parameter is defined to disable SMC-R function for the specified port range. Shared Memory Communications over Remote Direct Memory Access
V1R13 The jobname parameter can now include a 1-7 character prefix followed by a wildcard character (*), enabling all job names that match the prefix to access the ports in the range. Wildcard support for the PORTRANGE statement
SMFCONFIG V2R1 The SMCRGROUPSTATISTICS and the NOSMCRGROUPSTATISTICS parameters are defined to create SMF 119 subtype 41 interval records for SMC-R link group and link statistics. Shared Memory Communications over Remote Direct Memory Access
V2R1 The SMCRLINKEVENT and the NOSMCRLINKEVENT parameters are defined to create SMF 119 subtype 42 and subtype 43 event records for SMC-R link start and end events. Shared Memory Communications over Remote Direct Memory Access
V2R1 The IFSTATISTICS and the NOIFSTATISTICS parameters are updated to control the creation of the SMF 119 subtype 44 interval records for IBM 10 GbE RoCE Express interface statistics. Shared Memory Communications over Remote Direct Memory Access
SOMAXCONN V2R1 Default changed from 10 to 1024. Enhanced TCP protocol configuration options and default settings
TCPCONFIG V2R2
  • AUTODELAYACKS

    New parameter added to the existing DELAYACKS and NODELAYACKS parameters. Specification of this parameter causes the TCP/IP stack to autonomically determine whether to delay or immediately transmit an acknowledgment when a packet is received with the PUSH bit on in the TCP header.

  • QUEUEDRTT parameter

    The default value for the QUEUEDRTT parameter has changed from 20 to 0 milliseconds.

  • TCPMAXSENDBUFRSIZE parameter

    Ignored if Outbound right sizing (ORS) is active for a connection.

 TCP autonomic tuning enhancements
V2R1 Added the following new parameters:
  • CONNECTTIMEOUT
  • CONNECTINITINTERVAL
  • FRRTHRESHOLD
  • KEEPALIVEPROBES
  • KEEPALIVEPROBEINTERVAL
  • MAXIMUMRETRANSMITTIME
  • NAGLE and NONAGLE
  • QUEUEDRTT
  • RETRANSMITATTEMPTS
  • TCPMAXSENDBUFRSIZE
  • TIMEWAITINTERVAL
Enhanced TCP protocol configuration options and default settings
V2R1 SELECTIVEACK and NOSELECTIVEACK parameters are added. TCP support for selective acknowledgements
V2R1 The EPHEMERALPORTS parameter is added. User control of Ephmeral Port Ranges
TRANSLATE V2R2 Support for the HCH and NSAP parameters is removed because the HCH and ATM device types are no longer supported. Removal of support for legacy devices
UDPCONFIG V2R1 The EPHEMERALPORTS parameter is added. User control of Ephmeral Port Ranges
VIPARANGE V2R2 The TCP/IP stack can support up to 4096 configured and target DVIPA interfaces instead of 1024. Therefore, more dynamically created DVIPAs can be defined by using a VIPARANGE profile statement. Increase single stack DVIPA limit to 4096
V1R13 A new SAF parameter and its associated resname value are supported. You can use the SAF parameter to restrict the creation of a dynamic VIPA in the specified VIPARANGE subnet to permitted applications.

The maximum number of VIPARANGE statements for one stack is now 1024; prior to V1R13, the maximum number was 256.

 Improved security granularity for VIPARANGE DVIPAs
Parent topic: PROFILE.TCPIP configuration file