Use the INTERFACE statement for IPAQIDIO to configure IPv4 HiperSockets™ connectivity. Use the CHPID parameter to specify the value of the desired IQD CHPID that was configured within HCD. HiperSockets interfaces do not require a corresponding TRLE definition. Instead, the TRLE is dynamically built when the interface is started.
To determine the HiperSockets microcode level, use the DISPLAY TRL command. If a specific HiperSockets function is documented with a minimum microcode level, you can use this command to determine whether that function is supported. IBM® service might request the microcode level for problem diagnosis. For more information, see DISPLAY TRL command in z/OS Communications Server: SNA Operation.
Rule: Specify the required parameters in the order shown here. The Interface Definition parameters can be specified in any order.
Syntax
>>-INTERFace--intf_name-----------------------------------------> >--+-DEFINE--IPAQIDIO--| Interface Definition |-+-------------->< '---DELEte-----------------------------------' Interface Definition |--CHPID chpid--IPADDR--+-ipv4_address/0-------------+----------> +-ipv4_address---------------+ '-ipv4_address/num_mask_bits-' .-READSTORAGE GLOBAL---. >--+---------+--+---------+--+----------------------+-----------> '-IPBCAST-' '-MTU num-' '-READSTORAGE--+-MAX-+-' +-AVG-+ '-MIN-' >--+-----------+--+-------------------------------+-------------> '-VLANID id-' '-SOURCEVIPAINTerface vipa_name-' .-SECCLASS 255------------. .-NOMONSYSPLEX-. >--+-------------------------+--+--------------+----------------| '-SECCLASS security_class-' '-MONSYSPLEX---'
Parameters
- intf_name
- The name of the interface. The maximum length is 16 characters.
- DEFINE
- Specifies that this definition is to be added to the list of defined interfaces.
- DELETE
- Specifies that this definition is to be deleted from the list of defined interfaces. The intf_name must be the name of an interface that was previously defined by an INTERFACE statement. INTERFACE DELETE deletes the home IP address for the interface.
- IPAQIDIO
- Indicates that the interface is for HiperSockets IPv4.
- CHPID chpid
- Use this parameter to specify the IQD CHPID for the HiperSockets interface. This value is a 2-character hexadecimal value (00x - FFx). The hexadecimal value specified on the CHPID parameter cannot be the same value that is used for the dynamic XCF HiperSockets interface. See the IQDCHPID start option in the z/OS Communications Server: SNA Resource Definition Reference.
- IPADDR ipaddr_spec
- ipv4_address
- The home IP address for this interface.
Requirement: The IP address must be specified in dotted decimal form.
- num_mask_bits
- An integer value in the range 0 - 32 that represents the number
of leftmost significant bits for the subnet mask of the interface.
The default is 0.
Requirement: If you are configuring multiple IPv4 VLAN interfaces to the same HiperSockets CHPID, then you must specify a nonzero value for the num_mask_bits variable for each of these interfaces and the resulting subnet must be unique for each of these interfaces.
Rule: If you are using OMPROUTE and OMPROUTE is not configured to ignore this interface, ensure that the subnet mask value that you define on this parameter matches the subnet mask used by OMPROUTE for this interface. The subnet mask used by OMPROUTE is the subnet mask value defined on the corresponding OMPROUTE statement (OSPF_INTERFACE, RIP_INTERFACE, or INTERFACE) for this interface. If no OMPROUTE statement is specified for this interface, the subnet mask used by OMPROUTE is the class mask for the interface IP address.
- IPBCAST
- Specifies that the interface both sends and receives IP broadcast packets. If this parameter is not specified, no IP broadcast packets are sent or received on this interface.
- MTU num
- The maximum transmission unit (MTU), in bytes. This value can
be in the range 576 - 57344. The minimum MTU for IPv4 is 576. The
stack takes the minimum of the configured value and the firmware supported
value (which is the IQD frame size configured in HCD minus 8192)
The MTU default is equal to the IQD frame size minus 8192.
Rule: If you are using OMPROUTE and OMPROUTE is not configured to ignore this interface, ensure that the MTU that you define on this parameter matches the MTU used by OMPROUTE for this interface. The MTU used by OMPROUTE is the MTU value defined on the corresponding OMPROUTE statement (OSPF_INTERFACE, RIP_INTERFACE, or INTERFACE) for this interface. If an MTU value is not defined on the corresponding OMPROUTE statement for this interface or if no OMPROUTE statement is specified for this interface, the MTU used by OMPROUTE is the minimum MTU for IPv4 (576).
Tip: See Determining the maximum transmission unit in z/OS Communications Server: IP Configuration Guide for more information about how TCP/IP uses the MTU to determine the largest size frame to send.
- READSTORAGE
- An optional parameter that indicates the amount of fixed storage
that z/OS® CS should keep available
for read processing for this interface. The IQDIOSTG VTAM® start option allows you to
specify a value that applies to all HiperSockets interfaces. You
can use the READSTORAGE keyword to override the global IQDIOSTG value
for this interface based on the inbound workload that you
expect over this interface on this stack. The following values
are valid:
- GLOBAL
- The amount of storage is determined by the IQDIOSTG VTAM start option. This is the default value.
- MAX
- Use this value if you expect a heavy inbound workload over this interface.
- AVG
- Use this value if you expect a medium inbound workload over this interface.
- MIN
- Use this value if you expect a light inbound workload over this interface.
Tip: See the description of the IQDIOSTG VTAM start option in the z/OS Communications Server: SNA Resource Definition Reference for details about exactly how much storage is allocated by z/OS Communications Server for each of these values. - VLANID id
- An optional parameter followed by a decimal number indicating the virtual LAN identifier to be assigned to this HiperSockets interface. The valid range is 1 - 4 094.
- SOURCEVIPAINTERFACE vipa_name
- An optional parameter used to specify which previously-defined
VIPA interface is to be used for SOURCEVIPA (when IPCONFIG SOURCEVIPA
is in effect). The vipa_name value is the
interface name for a VIRTUAL interface.
Requirement: The VIRTUAL interface or the link must be defined prior to specifying this INTERFACE statement to the TCP/IP stack. It must either already be defined, or the INTERFACE statement (or DEVICE and LINK statements) that define the static VIPA must precede this INTERFACE statement in the profile data set.
Tip: The use of the SOURCEVIPAINTERFACE parameter can be overridden. See the information about Source IP address selection in z/OS Communications Server: IP Configuration Guide for the hierarchy of ways that the source IP address of an outbound packet is determined. - SECCLASS security_class
- Use this parameter to associate a security class for IP filtering
with this interface. For traffic over the interface to match a filter
rule, the filter rule must have the same security class value as the
interface or a value of 0. Filter rules can be specified in the TCP/IP
profile or in an IP Security policy file that is read by the Policy
Agent. Filter rules can include a security class specification on
the IpService statement in an IP Security policy file or on the SECCLASS
parameter on the IPSECRULE statement in the TCP/IP profile.
Valid security classes are identified as a number in the range 1 - 255. The default value is 255. See security class values in z/OS Communications Server: IP Configuration Guide for more information.
Restriction: The TCP/IP stack ignores this value if IPSECURITY is not specified on the IPCONFIG statement.
- MONSYSPLEX | NOMONSYSPLEX
- Specifies whether or not sysplex autonomics should monitor the
interface's status.
- NOMONSYSPLEX
- Specifies that sysplex autonomics should not monitor the interface's status. This is the default value.
- MONSYSPLEX
- Specifies that sysplex autonomics should monitor interface's status.
Restriction: The MONSYSPLEX attribute is not in effect unless the MONINTERFACE keyword is specified on the GLOBALCONFIG SYSPLEXMONITOR profile statement. The presence of dynamic routes over the interface is monitored if the DYNROUTE keyword is also specified on the GLOBALCONFIG SYSPLEXMONITOR profile statement.
Steps for modifying
See Summary of INTERFACE statements for modification information.
Examples
INTERFACE HIPERSOCK1 DEFINE IPAQIDIO CHPID FC
IPADDR 9.1.1.1/24