Steps for converting from IPv4 VIRTUAL DEVICE, LINK, and HOME definitions to the IPv4 VIRTUAL INTERFACE statement

You can use the INTERFACE statement in the TCP/IP profile to configure IPv4 definitions for static VIPAs rather than using the DEVICE, LINK, and HOME statements. Using the INTERFACE statement simplifies stack configuration for VIRTUAL interfaces.

Before you begin

If a static VIPA is being used as a source VIPA for any IPv4 interfaces that are configured using DEVICE and LINK statements, then you cannot convert that static VIPA to an IPv4 INTERFACE statement.

Procedure

Perform the following steps to convert your TCP/IP profile so that it uses the INTERFACE statement to configure IPv4 definitions for static VIPAs.

Convert the IPv4 VIRTUAL DEVICE, LINK, and HOME statements to an IPv4 VIRTUAL INTERFACE statement. The values used in the following substeps are based on the sample profile shown in Figure 1.
1. Copy the LINK name (VIPA1 in the example) and specify this name as the interface name on the INTERFACE statement.
  Tip: When you use the original LINK name as the new INTERFACE name, you do not have to change OMPROUTE definitions or the PRIMARYINTERFACE statement.
2. Copy the VIRTUAL parameter from the LINK statement and specify this parameter after the DEFINE parameter of the INTERFACE statement.
3. Copy the HOME list entry IP address (201.16.1.1 in the example) and specify this address on the IPADDR parameter of the INTERFACE statement.
4. Remove the HOME list entry.
Figure 1. Examples of the profile before and after conversion
Example of the profile before conversion:
```
            DEVICE VIPA    VIRTUAL   0 
            LINK      VIPA1  VIRTUAL   0   VIPA
            ;
            HOME
             201.16.1.1     VIPA1
```
Example of the profile after conversion:
```
            INTERFACE VIPA1
             DEFINE VIRTUAL
             IPADDR 201.16.1.1
```
Tip: Optionally, you can dump the TCP/IP address space and use the CONVERT parameter on the TCPIPCS PROFILE subcommand to display the configuration information at the time of the dump. The resulting output reflects your IPAQENET, IPAQIDIO, and VIRTUAL DEVICE, LINK, and HOME definitions in INTERFACE statement format, which might be helpful in converting your profile to use INTERFACE statements. Review the output before you implement any changes. For more information about using the CONVERT parameter on the TCPIPCS PROFILE subcommand, see z/OS Communications Server: IP Diagnosis Guide.

For more information about the IPv4 VIRTUAL INTERFACE statement, see z/OS Communications Server: IP Configuration Reference.
Remove any BSDROUTINGPARMS entries for the interface.

Results

For information about the TCP/IP profile (PROFILE.TCPIP) and configuration statements, see z/OS Communications Server: IP Configuration Reference.