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 address of the X.25 NPSI interface program devices that you use. Use the LINK statement to define a network interface link associated with the X.25 NPSI interface program devices.
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.
.-NOAUTORestart-. >>-DEVICE--device_name--X25NPSI--proc_name--+---------------+-->< '-AUTORestart---'
Parameters
- device_name
- The name of the device. The maximum length is 16 characters. The same name is specified in the LINK statement.
- X25NPSI
- Specifies that the device is an X.25 NPSI.
- proc_name
- The name of the X.25 NPSI server started procedure. The maximum length is eight characters.
- 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.
Restriction: Only one DEVICE and LINK statement per TCPIPX25 address space is allowed.
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.
- SAMEHOST
- Specifies that the connection to X.25 NPSI is established using
a SAMEHOST connection.
Note on IUCV: The IUCV keyword remains for migration purposes and is identical to SAMEHOST.
- link_number
- The link_number must be an integer, but its value is ignored. This parameter is included for consistency with LINK statement formats for other device types.
- device_name
- The device_name must be the same as specified in the DEVICE statement. The maximum length is 16 characters.
- 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 2 147 483 647. The default is 56 000. 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 2 147. The default is 0. 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.
Examples
DEVICE X25DEV X25NPSI TCPIPX25
LINK X25LINK SAMEHOST 1 X25DEV
;
HOME
199.005.058.23 X25LINK
;
GATEWAY
;
; Network First Hop Link name Packet size Subnet mask Subnet Value
192.005 = X25LINK 2000 0.0.255.0 0.0.58.0
;
START X25DEV
;Usage notes
To use dynamic routing with this device, see the NBMA subnetworks information in z/OS Communications Server: IP Configuration Guide.