Unlike static VIPAs, DVIPAs are not configured by using DEVICE,
LINK, and HOME statements (for IPv4) or by using INTERFACE statements
(for IPv6). The configuration statements for the DVIPA support are
contained within the VIPADYNAMIC block and consist of the following
statements:
- VIPADEFINE and VIPABACKUP statements that are used to configure
DVIPAs to be dynamically moved from a failing TCP/IP to a backup TCP/IP
- VIPARANGE used to specify a range of IP addresses which can be
dynamically activated as a VIPA by an application program
- VIPADELETE used to delete existing DVIPAs
- VIPADISTRIBUTE used to configure a DVIPA as a distributed DVIPA
and designate the target stacks
The following topics discuss how these statements are used to provide
the DVIPA support. For syntax details, see z/OS Communications Server: IP Configuration
Reference. For more information, see IBM® z/OS® V1R13
Communications Server TCP/IP Implementation, Volume 3: High Availability,
Scalability, and Performance, SG24–7998.
When dynamically created DVIPAs are deleted, any applications that
are bound to those DVIPAs (VIPARANGE or MODDVIPA) receive an asynchronous
error, EUNATCH (3448) - the protocol required to support the address
family is unavailable.