VIPADYNAMIC statement summary

Use the VIPADYNAMIC statement to start a block of definitions related to dynamic VIPAs (DVIPAs) and the sysplex distributor; use an ENDVIPADYNAMIC statement to end the block of definitions. A VIPADYNAMIC block can contain the following statements:

• VIPADYNAMIC - VIPADEFINE statement
• VIPADYNAMIC - VIPABACKUP statement
• VIPADYNAMIC - VIPADELETE statement
• VIPADYNAMIC - VIPADISTRIBUTE statement
• VIPADYNAMIC - VIPARANGE statement
• VIPADYNAMIC - VIPAROUTE statement
• VIPADYNAMIC - VIPASMPARMS statement

Rules:

• Within a single profile there should be only one VIPADEFINE or VIPABACKUP statement for a particular DVIPA. If the DVIPA does appear in more than one statement, a VIPADELETE statement must be specified before the last instance to ensure that it is not rejected.
• A stack is limited to no more than 1024 configured or target VIPAs at any one time. A configured dynamic VIPA is one that was created in any of the following ways, and might or might not be active:
  • Using VIPADEFINE
  • Using VIPABACKUP
  • Using an IOCTL SIOCSVIPA or SIOCSVIPA6 DEFINE value when this stack had a covering VIPARANGE statement
  • Using a BIND when this stack had a covering VIPARANGE statement
• Syntax errors in a VIPADYNAMIC block end further processing of the VIPADYNAMIC block. VIPADYNAMIC statements are processed up to the syntax error, and any remaining statements are ignored.
• The TCP/IP stack does not maintain interface counters for dynamic VIPA interfaces.

Related topics

• See z/OS Communications Server: IP Configuration Guide for more information about Virtual IP Addressing.
• IPCONFIG statement.
• IPCONFIG6 statement.