Use the DEVICE statement to specify the device name of a static virtual device, and use the LINK statement to define the link on the DEVICE statement.
More than one virtual DEVICE/LINK statement can be defined to allow for multiple virtual IP addresses on one TCP/IP image in one MVS™ system.
Tip: You can also use the INTERFACE statement to define an IPv4
interface for a static VIPA, which combines the definitions of the
DEVICE, LINK, and HOME statements into a single statement.
This statement applies to IPv4. See INTERFACE — VIRTUAL6 interfaces statement for this function in IPv6.
Syntax
Rule: Specify the parameters in the order shown here.
>>-DEVice--device_name--VIRTual--device_number-----------------><
Parameters
- device_name
- The name of the device. The maximum length is 16 characters. The same name is specified in the LINK statement.
- VIRTUAL
- Specifies that the device is not associated with real hardware and is used for fault tolerance support. The static virtual devices always stay active and are never subject to physical failure.
- device_number
- The device_number must be a hexadecimal number, but the value is ignored. This parameter is included for consistency with the DEVICE statements for other device types.
Syntax
Restriction: Only one LINK statement can be defined for each virtual device.
Parameters
- link_name
- The name of the link. The maximum length is 16 characters. The same name is specified in the HOME statement.
- VIRTUAL
- Specifies that the link is a virtual link that is not associated with real hardware and is used for fault tolerance support.
- adapter_address
- The adapter_address must be an integer, but the value is ignored. This parameter is included for consistency with the LINK statements for other device types.
- device_name
- The device_name must be the same as specified in the DEVICE statement.
Steps for modifying
See Modifying DEVICE and LINK statements for modifying information.
Guideline: The steps in the Modifying DEVICE and LINK statements topic that refer to stopping and starting the device do not apply to virtual devices.
Examples
DEVICE VDEV1 VIRTUAL 0
LINK VLINK1 VIRTUAL 0 VDEV1
DEVICE VDEV2 VIRTUAL 1
LINK VLINK2 VIRTUAL 0 VDEV2Usage notes
- The device_name or link_name values should not start with VIP because VIP is a restricted keyword.
- A virtual LINK cannot be coded on the START, BEGINROUTES, GATEWAY or TRANSLATE statements, but can be coded on a BSDROUTINGPARMS statement for interface characteristics such as subnet mask.
Requirement: If you are running with 3172s configured
for multihost connectivity (release 3.5 and later) and want to use
VIPA addresses on the host, you must configure the 3172 in one of
the following ways:
- As a default router (routes all IP addresses)
- Configure all VIPA addresses in the 3172
- For rules on defining virtual IP addresses for virtual links, see HOME statement.