Use the GLOBALCONFIG statement to pass global configuration parameters to TCP/IP.
Tip: Specify the parameters for this statement in any order.
>>-GLOBALCONFig-------------------------------------------------> .----------------------------------------------------------------. V | >----+------------------------------------------------------------+-+->< | .-ALLTRAFFIC--. | | .-AUTOIQDX--+-------------+-. | | | '-NOLARGEDATA-' | | +-+---------------------------+------------------------------+ | '-NOAUTOIQDX----------------' | | .-ECSALimit 0K----------------. | +-+-----------------------------+----------------------------+ | '-+-ECSALimit --ecsa_limitK-+-' | | '-ECSALimit --ecsa_limitM-' | | .-NOEXPLICITBINDPORTRANGE------------------. | +-+------------------------------------------+---------------+ | '-EXPLICITBINDPORTRANGE 1st_port num_ports-' | | .-NOIQDMULTIWRITE-. | +-+-----------------+----------------------------------------+ | '-IQDMULTIWRITE---' | +-+-------------------+--------------------------------------+ | '-IQDVLANid vlan_id-' | | .-MAXRECS 100------. | +-+------------------+---------------------------------------+ | '-+-MAXRECS *----+-' | | '-MAXRECS recs-' | | .-NOMLSCHKTERMinate-. | +-+-------------------+--------------------------------------+ | '-MLSCHKTERMinate---' | | .-POOLLimit 0K----------------. | +-+-----------------------------+----------------------------+ | '-+-POOLLimit --pool_limitK-+-' | | '-POOLLimit --pool_limitM-' | | .-NOSEGMENTATIONOFFLoad-. | +-+-----------------------+----------------------------------+ | '-SEGMENTATIONOFFLoad---' | | .-NOSMCR-------------------------------------------------. | +-+--------------------------------------------------------+-+ | | .-----------------------------------------------. | | | | V | | | | '-SMCR---+-------------------------------------------+-+-' | | | .---------------------------------------. | | | | | .----------------------. | | | | | V V | | | | | +---PFID - pfid----+------------------+-+-+-+ | | | | .-PORTNum -1---. | | | | | +-+--------------+-+ | | | | | '-PORTNum -num-' | | | | | | .-MTU -1024----. | | | | | '-+--------------+-' | | | | '-MTU -mtusize-' | | | | .-FIXEDMemory--256------. | | | +---+-----------------------+---------------+ | | | '-FIXEDMemory--mem_size-' | | | | .-TCPKEEPmininterval--300------. | | | '---+------------------------------+--------' | | '-TCPKEEPmininterval--interval-' | | .-SYSPLEXMONitor--| Sysplex options |-. | +-+-------------------------------------+--------------------+ | '-SYSPLEXMONitor--| Sysplex options |-' | | .-SYSPLEXWLMPoll 60------. | +-+------------------------+---------------------------------+ | '-SYSPLEXWLMPoll seconds-' | | .-NOTCPIPStatistics-. | +-+-------------------+--------------------------------------+ | '-TCPIPStatistics---' | | .-NOWLMPRIORITYQ---------------------------. | +-+------------------------------------------+---------------+ | | .-default_control_values-. | | | '-WLMPRIORITYQ--+------------------------+-' | | '-IOPRIn control_values--' | +-+-------------------+--------------------------------------+ | '-XCFGRPid group_id-' | '-+-------------------------------------+--------------------' | .---------------------------. | | V .-NOIPSECURITY-. | | '-ZIIP----+-+--------------+------+-+-' | '-IPSECURITY---' | | .-NOIQDIOMULTIWRITE-. | '-+-------------------+-' '-IQDIOMULTIWRITE---'
Sysplex options .-NOAUTOREJOIN-. |--+-+--------------+-------------------+-----------------------| | '-AUTOREJOIN---' | | .-NODELAYJOIN-. | +-+-------------+--------------------+ | '-DELAYJOIN---' | +-+--------+-------------------------+ | '-NOJOIN-' | | .-NOMONINTERFACE NODYNROUTE------. | +-+--------------------------------+-+ | | .-NODYNROUTE-. | | | +-NOMONINTERFACE--+------------+-+ | | | .-DYNROUTE---. | | | '-MONINTERFACE--+------------+---' | | '-NODYNROUTE-' | | .-NORECOVERY-. | +-+------------+---------------------+ | '-RECOVERY---' | | .-TIMERSECS 60------. | '-+-------------------+--------------' '-TIMERSECS seconds-'
See Steps for modifying for details about changing this parameter while the TCP/IP stack is active. See z/OS Communications Server: IP Configuration Guide for information about the intraensemble data network and the dynamic IQDX function.
ECSALIMIT ensures that TCP/IP does not overuse common storage. It is intended to improve system reliability by limiting TCP/IP's storage usage. The limit must account for peak storage usage during periods of high system activity or TCP/IP storage abends might occur. The limit does not include storage used by communications storage manager (CSM). CSM ECSA storage is managed independently of the TCP/IP ECSALIMIT. See z/OS Communications Server: SNA Network Implementation Guide for more information about CSM.
Specifying a nonzero ECSALIMIT enables warning messages EZZ4360I, EZZ4361I, and EZZ4362I to appear if a storage shortage occurs.
Use this parameter so that you can specify distributed DVIPAs as the source IP address on DESTINATION or JOBNAME rules in a SRCIP block. See SRCIP statement.
Restriction: In a common INET (CINET) environment, this parameter is accepted, but the EXPLICITBINDPORTRANGE function is supported in a limited set of conditions only. It is supported when CINET is managing one stack only on the system or when the affected application has established stack affinity. Otherwise, results can be unpredictable.
Restriction: HiperSockets multiple write is effective only on an IBM® System z10™ or later and when z/OS® is not running as a guest in a z/VM® environment.
See the modifying information in this topic for details about changing this parameter while the TCP/IP stack is active. See the HiperSockets multiple write information in z/OS Communications Server: IP Configuration Guide for more information about HiperSockets multiple write support.
The specified value, vlan_id, is used for both IPv4 and IPv6 DYNAMICXCF HiperSockets connectivity. This parameter is intended to be used in conjunction with the GLOBALCONFIG XCFGRPID parameter to support subplexing.
Subplexing enables TCP/IP participation in a Sysplex to be partitioned into subsets based on the XCFGRPID value. When using subplexing, TCP/IP stacks with the same XCFGRPID value should specify the same IQDVLANID value. Stacks with different XCFGRPID values should have different IQDVLANID values. If you have stacks in the default subplex (that is, stacks that do not specify an XCFGRPID value) that use the same HiperSockets CHPID as stacks within a non-default subplex (an XCFGRPID value was specified), then the stacks in the default subplex should specify an IQDVLANID value that is different from the other IQDVLANID values specified by the other non-default subplex stacks that use the same HiperSockets CHPID.
Restriction: The IQDVLANID parameter can be specified only in the initial profile.
Valid VLAN IDs are in the range 1 - 4094. For more information about VLANs and Hipersockets see z/OS Communications Server: IP Configuration Guide.
Informational message EZD1217I is written to the system console summarizing the number of problems found. Additional informational messages between EZD1219I and EZD1234I are written to the job log for each configuration inconsistency found.
This is the default value.
Informational message EZD1217I is written to the system console summarizing the number of problems found. Additional informational messages between EZD1219I and EZD1234I are written to the job log for each configuration inconsistency found.
POOLLIMIT ensures that TCP/IP does not overuse its authorized private storage. Most systems can use the default POOLLIMIT (no limit). Systems with limited paging capacity can use POOLLIMIT to help limit TCP/IP storage usage. If the limit is used, it must account for peak storage usage during periods of high system activity or TCP/IP storage abends might occur.
POOLLIMIT can be higher than the REGION size on the TCP/IP start procedure because POOLLIMIT applies to authorized storage, whereas REGION applies to unauthorized storage. Specifying a nonzero POOLLIMIT enables warning messages EZZ4364I, EZZ4365I, and EZZ4366I to appear if a storage shortage occurs.
See the Modifying topic for information about changing this parameter while the TCP/IP stack is active. See TCP segmentation offload information in z/OS Communications Server: IP Configuration Guide for more information about TCP segmentation offload support.
For example, if PFID 0013 and PFID 0014 are both defined in HCD to represent the RNIC adapter with PCHID value 0140, you can configure PFID 0013 PORT 1 PFID 0014 PORT 2 to use both ports on the RNIC adapter. However, if you specify PFID 0013 PORT 1 PFID 0013 PORT 2, only the first port that is activated will be used.
For more information about TCP keepalive processing for the TCP path and the SMC-R path of SMC-R links, see TCP keepalive in z/OS Communications Server: IP Configuration Guide.
If the SYSPLEXMONITOR parameter is not specified in the initial TCP/IP profile, then the sysplex autonomics function uses the default values for all SYSPLEXMONITOR subparameters. If the SYSPLEXMONITOR parameter is specified but not all subparameters are specified in the initial TCP/IP profile, then the sysplex autonomics function uses the default values for those SYSPLEXMONITOR subparameters that are not specified. For example, if SYSPLEXMONITOR is specified without RECOVERY or NORECOVERY specified in the initial profile, then the NORECOVERY action is in effect.
Rule: If you specify the GLOBALCONFIG statement in a data set associated with a VARY TCPIP,,OBEYFILE command and the SYSPLEXMONITOR parameter is specified without any subparameters, an informational message is issued and the parameter is ignored.
Restriction: AUTOREJOIN cannot be configured when NORECOVERY is configured (or set to the default value).
Guideline: AUTOREJOIN should be used when RECOVERY is configured to allow the stack to rejoin the sysplex group without operator intervention.
Tip: This level of monitoring is useful in detecting problems that OMPROUTE is having in communicating with other routing daemons on the selected network interfaces.
If no dynamic routes are present in the TCP/IP stack from that network, a specific interface attached to that network might not be active or routers attached to that network might not be active or healthy. In either case, when these conditions are detected, they provide a reasonable indication that client requests for DVIPAs or distributed DVIPAs owned by this TCP/IP stack might not reach this stack over that interface. These checks can help further qualify the state of a network interface on this TCP/IP stack. When the MONINTERFACE parameter is specified, This is the default value.
Restriction: DYNROUTE cannot be specified when NOMONINTERFACE is configured (or is the default value).
If you subsequently issue a VARY TCPIP,,SYSPLEX,JOINGROUP command, the NOJOIN setting is overridden and the saved GLOBALCONFIG SYSPLEXMONITOR parameter settings become active. For example, if you configure NOJOIN and DELAYJOIN, DELAYJOIN is initially ignored. If you subsequently issue a V TCPIP,,SYSPLEX,JOINGROUP command, NOJOIN is overridden, DELAYJOIN becomes active, and the stack joins the sysplex group if OMPROUTE is initialized.
Any sysplex-related definitions within the TCP/IP profile, such as VIPADYNAMIC or IPCONFIG DYNAMICXCF statements, are not processed until the TCP/IP stack joins the sysplex group.
Restriction: You can specify this parameter only in the initial profile; you cannot specify it when you issue a VARY TCPIP,,OBEYFILE command.
Guideline: This level of monitoring can further qualify the health of the TCP/IP stack by ensuring that at least one key interface is active and available. This option can be useful in environments where the dynamic XCF interface is not configured as an alternate network path for this stack (for example, where no dynamic routes are advertised over dynamic XCF interfaces and no static or replaceable static routes are defined over those interfaces).
Recovery is the preferred method of operation because other members of the TCP/IP sysplex can automatically take over the functions of a member with no actions needed by an operator. IBM Health Checker for z/OS enhancements can be used to check whether the RECOVERY parameter has been specified when the IPCONFIG DYNAMICXCF or IPCONFIG6 DYNAMICXCF parameters have been specified. For more details about IBM Health Checker for z/OS enhancements, see the IBM Health Checker for z/OS enhancements information in the z/OS Communications Server: IP Diagnosis Guide.
The NOTCPIPSTATISTICS parameter is confirmed by the message:
EZZ0613I TCPIPSTATISTICS IS DISABLED
This
is the default value.The TCPIPSTATISTICS parameter is confirmed by the message:
EZZ0613I TCPIPSTATISTICS IS ENABLED
The SMFCONFIG TCPIPSTATISTICS parameter (see SMFCONFIG statement) serves a different purpose. It requests that SMF records of subtype 5 containing TCP/IP statistics be created. These statistics are recorded in SMF type 118 or 119, subtype 5 records.
You can assign specific OSA-Express QDIO write priority values by using the IOPRIn subparameters, where n is one or more of the priority values in the range 1 - 4. For each subparameter, you can specify a control value in the range 0 - 6, which correlates to the WLM services classes, or you can specify the keyword FWD for forwarded packets. WLM supports a service class for the SYSTEM value, but this value is always assigned the OSA-Express QDIO write priority 1 and its assignment cannot be configured; therefore, a control value is not assigned for the SYSTEM WLM service class.
You can use the default assignment by specifying the WLMPRIORITYQ parameter without any IOPRIn subparameters. See the description of the default_control_values variable in this topic to understand the default assignment.
Control value | Type of packet | Default QDIO priority |
---|---|---|
0 | System-defined service class (SYSSTC) used for high-priority started tasks | 1 |
1 | User-defined service classes with importance level 1 | 2 |
2 | User-defined service classes with importance level 2 | 3 |
3 | User-defined service classes with importance level 3 | 3 |
4 | User-defined service classes with importance level 4 | 4 |
5 | User-defined service classes with importance level 5 | 4 |
6 | User-defined service classes associated with a discretionary goal | 4 |
FWD | Forwarded packets | 4 |
WLMPRIORITYQ IOPRI1 0 1
IOPRI2 2 FWD
IOPRI3 3 4
IOPRI4 5 6
These characters are also used as a suffix for the EZBDVIPA and EZBEPORT structure names, in the form EZBDVIPAvvtt and EZBEPORTvvtt. If no VTAM XCF group ID suffix was specified, the structure names are EZBDVIPA01tt and EZBEPORT01tt.
If XCFGRPID is not specified, the XCF group name is EZBTvvCS and the structure names are EZBDVIPAvv and EZBEPORTvv. If no VTAM XCF group id suffix was specified, the group name is EZBTCPCS and the structure names are EZBDVIPA and EZBEPORT.
Restriction: XCFGRPID can be specified only in the initial profile.
This allows multiple TCP/IP stacks to join separate Sysplex groups and access separate Coupling Facility structures, isolating sets of TCP/IP stacks into subplexes with XCF communication only with other TCP/IP stacks within the same subplex.
If HiperSockets is supported on this system, the IQDVLANID parameter, on the GLOBALCONFIG statement, must be specified if XCFGRPID is specified. Stacks on the same CPC using the same HiperSockets CHPID that specify the same XCFGRPID value must specify the same IQDVLANID value.
Stacks on the same CPC using the same HiperSockets CHPID specifying different XCFGRPID values must specify different IQDVLANID values. This allows partitioning of connectivity across the Sysplex to include partitioning of connectivity across HiperSockets.
Creating TCP/IP and VTAM subplexes can add some complexity to your VTAM and TCP/IP configurations and requires careful planning. Before setting this parameter you should review the information about setting up a subplex in the z/OS Communications Server: IP Configuration Guide.
Tip: These ZIIP parameters apply to pre-defined HiperSockets interfaces, as well as HiperSockets interfaces that are created and used by dynamic XCF definitions.
To modify parameters for the GLOBALCONFIG statement, you must respecify the statement with the new parameters.
The following list describes how to modify individual parameters:
If you use the VARY TCPIP,,OBEYFILE command to change this parameter from NOAUTOIQDX to AUTOIQDX, active OSX interfaces are not affected, but the stack will attempt to activate a dynamic IQDX interface on any subsequent OSX activations.
If you specified the NOEXPLICITBINDPORTRANGE parameter and then you change to the EXPLICITBINDPORTRANGE parameter, then a range of ports used for the EXPLICITBINDPORTRANGE pool is set. The stack uses ports from that pool for explicit bind() requests to the IPv4 INADDR_ANY address, or to the IPv6 unspecified address (in6addr_any), and port 0. If the range specified on the EXPLICITBINDPORTRANGE parameter is different from the currently active range for the EXPLICITBINDPORTRANGE pool in the coupling facility, the new range replaces that value.
Changing the starting port (1st_port), the number of ports (num_ports), or both for the EXPLICITBINDPORTRANGE parameter changes the port numbers in the pool of ports that is guaranteed to be unique across the sysplex for future port allocation
Changing from NODELAYJOIN to DELAYJOIN has no immediate effect until the TCP/IP stack leaves the sysplex group and then attempts to rejoin while OMPROUTE is not active.
Rule: You cannot modify individual IOPRIn control values. If you attempt to modify IOPRIn control values, but you specify only those control values that you want to modify, then the QDIO priority 4 is assigned to packets that are associated with any control values that you omitted.
GLOBALCONFIG SYSPLEXMONITOR AUTOREJOIN DELAYJOIN MONINTERFACE DYNROUTE RECOVERY
The following example shows the use of the EXPLICITBINDPORTRANGE parameter to define 1024 ports in the range 5000 - 6023. The ports are used for explicit binds to the IPv4 INADDR_ANY address, or to the IPv6 unspecified address (in6addr_any), and port 0:
GLOBALCONFIG EXPLICITBINDPORTRANGE 5000 1024
The following example shows the use of the SMCR parameter to define two 10GbE RoCE Express features that use PFID values 0018 and 0019 and port numbers 1 and 2, and to limit the stack to 500 megabytes of 64-bit storage for SMC-R communications.
GLOBALCONFIG SMCR PFID 0018 PORTNUM 1 PFID 0019 PORTNUM 2 FIXEDMEMORY 500