This
device type will not be supported in a future release. It is recommended
that you migrate to a later interface type, such as OSA-Express QDIO
or HiperSockets™.
Use the DEVICE statement to specify the name and hexadecimal device number of the channel data link control (CDLC) devices that you use. Use the LINK statement to define a network interface link associated with the CDLC devices.
- NCP V7R3 or earlier does not support native IP transmission
across the channel of the transport PDUs associated with RIP traffic
(NCP V7R3 or earlier expects these PDUs to be carried in SNA Frames).
SNALINK is still required in environments where dynamic routing is
performed with the NCP V7R3 or earlier (using NCPROUTE).
To minimize the amount of data sent across the SNALINK (LUO) connection (as SNALINK consumes more CPU than does IP over CDLC), use the RIP Filter to send RIP updates across the channel, while the associated transport PDUs (Route Table Management, for example, Handshaking, Add Route Request, Delete Route Request) are carried over the SNALINK connection.
- If the device is running a later version than NCP V7R3, or if the device is a 3746 model 950, SNALINK is not required (all IP and RIP traffic can be transported over direct CDLC link of TCP/IP).
For more information about missing interrupt handler (MIH) considerations with TCP/IP devices, see Missing interrupt handler factors.
Syntax
Rule: Specify the parameters in the order shown here.
.-15-----------. >>-DEVICE--device_name--CDLC--device_number--+--------------+---> '-read_buffers-' .-15------------. .-4096------. .-4096-------. >--+---------------+--+-----------+--+------------+-------------> '-write_buffers-' '-read_size-' '-write_size-' .-NOAUTORestart-. >--+---------------+------------------------------------------->< '-AUTORestart---'
Parameters
- device_name
- The name of the device. The maximum length is 16 characters. The same name is specified in the LINK statement.
- CDLC
- Specifies that this device is to run the CDLC protocol.
- device_number
- The hexadecimal device number (in the range 0 - FFFF) of the CDLC device.
- read_buffers
- The decimal number of buffers to allocate to the read channel program. The default is 15. The minimum is 1 and the maximum is 63. The product of read_buffers times read_size must be less than or equal to 65535. If the product of these configured variables exceeds 65535, TCP/IP reduces read_buffers to the integer 65535/read_size.
- write_buffers
- The decimal number of buffers to allocate to the write channel program. The minimum is 1 and the maximum is 63. The product of write_buffers times write_size must be less than or equal to 65535. The default is 15. If the product of these configured variables exceeds 65535, TCP/IP reduces write_buffers to the integer 65535/write_size.
- read_size
- The size in bytes (decimal) of the read buffers. The default is 4096. Valid values are 1024, 2048, 4096, 6144, 8192.
- write_size
- The size in bytes (decimal) of the write buffers. The default is 4096. Valid values are 1024, 2048, 4096, 6144, 8192.
- AUTORESTART | NOAUTORESTART
- Controls device failure reactivation behavior.
- NOAUTORESTART
- For most device failures, specifying NOAUTORESTART indicates that the TCP/IP address space does not attempt to reactivate this device.
- AUTORESTART
- In the event of a device failure, the TCP/IP address space attempts to reactivate the device. For more information, see Recovering from device failures.
Syntax
Rule: The optional parameters on the LINK statement following the device_name parameter can be specified in any order.
Parameters
- link_name
- The name of the link. The maximum length is 16 characters.
- CDLC
- Specifies that the link is a channel DLC.
- adapter_addr
- The adapter_addr value must be an integer, but the value is ignored. This parameter is included for consistency with the LINK statement formats for other device types.
- device_name
- The device_name must be the same as specified in the DEVICE statement.
- IFSPEED ifspeed
- An optional estimate of the interface's current bandwidth in bits per second. The minimum value that can be specified for ifspeed is 0; the maximum value is 2147483647. The default is 4500000. This value is accessible to SNMP for management queries, but has no effect on operation of the device.
- IFHSPEED ifhspeed
- An optional estimate of the interface's current bandwidth in one million bits per second units. The minimum value that can be specified for ifhspeed is 0; the maximum value is 2147. The default is 4. This value is accessible to SNMP for management queries, but has no effect on operation of the device.
- SECCLASS security_class
- Use this parameter to associate a security class for IP filtering
with this interface. In order 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 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 IPSEC statement in the TCP/IP profile.
Valid security classes are identified as a number in the range 1 - 255. The default value is 255. For more information about security class values, see z/OS Communications Server: IP Configuration Guide..
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
link's status.
- NOMONSYSPLEX
- Specifies that sysplex autonomics should not monitor the link's status. This is the default value.
- MONSYSPLEX
- Specifies that sysplex autonomics should monitor the link'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 this link is monitored if the DYNROUTE keyword is also specified on the GLOBALCONFIG SYSPLEXMONITOR profile statement.
Steps for modifying
See Modifying DEVICE and LINK statements for modifying information.
Usage notes
For a buffer size of 8192, the maximum number of buffers is 7. For a buffer size of 6144, the maximum number of buffers is 10. For a buffer size of 4096, the maximum number of buffers is 15. For a buffer size of 2048, the maximum number of buffers is 31. For a buffer size of 1024, the maximum number of buffers is 63.