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

Use the INTERFACE statement to configure IPv4 definitions for HiperSockets™, rather than using the DEVICE, LINK, and HOME statements. The INTERFACE statement simplifies stack configuration for IPAQIDIO interfaces, and some functions like multiple VLAN support require that the HiperSockets interface is defined with the INTERFACE statement.

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

1. Convert the IPv4 IPAQIDIO DEVICE, LINK, and HOME statements to an IPv4 IPAQIDIO INTERFACE statement. The values used in the following substeps are based on the sample profiles shown in Figure 1 and Figure 2.
   1. Copy the LINK name (HSINTF1 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 the static route definitions, OMPROUTE definitions, PKTTRACE statement, and PRIMARYINTERFACE statement.
   2. Copy the IPAQIDIO parameter from the LINK statement and specify this parameter after the DEFINE parameter of the INTERFACE statement.
   3. Copy the remaining LINK parameters and values (IPBCAST in the example) to the INTERFACE statement.
   4. Copy the xx portion of the DEVICE name (FE in the example) and specify this value on the CHPID parameter of the INTERFACE statement.
   5. Copy the HOME list entry IP address (200.16.1.1 in the example) and specify this address on the IPADDR parameter of the INTERFACE statement.
   6. Append a value (/24 in the example) to the end of the IP address to define the subnet mask.
   7. Remove the HOME list entry.
   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 IPAQIDIO INTERFACE statement, see z/OS Communications Server: IP Configuration Reference.

2. Remove any BSDROUTINGPARMS entries for the interface.
3. If you configured the SOURCEVIPA parameter on the IPCONFIG statement, perform the following steps:
   1. Find the IPAQIDIO LINK in the original HOME list and search backwards to locate the static VIPA (if any) that is located closest to this link in the HOME list.
   2. If you find a static VIPA, add the SOURCEVIPAINTERFACE parameter to the IPv4 INTERFACE statement. Use the static VIPA link name as the SOURCEVIPAINTERFACE value.
4. If you are using the START statement to start the IPv4 device, change the START statement to specify the name of the IPv4 INTERFACE.
5. If you are using the GATEWAY statement to configure any static routes over the interface, convert the GATEWAY statement to a BEGINROUTES block.
   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 GATEWAY definitions in the format of a BEGINROUTES block, which might be helpful in converting your profile to use BEGINROUTES. Review the output before you implement any changes. For more information about using the TCPIPCS PROFILE subcommand, see z/OS Communications Server: IP Diagnosis Guide.
6. Ensure that your HCD configuration is sufficient for the resulting dynamic TRLE definitions. DEVICE/LINK and IPv6 INTERFACE definitions use the IUTIQDxx TRLE and the new IPv4 INTERFACE definitions use the IUTIQ4xx TRLE where xx is the HiperSockets CHPID. If you use a combination of these definitions for a HiperSockets CHPID that requires both TRLEs, configure an additional set of 10 IQD devices in HCD for the new TRLE. If you are converting from DEVICE/LINK to IPv4 INTERFACE and are not using IPv6, you can reuse the same set of IQD devices for the new TRLE. However, if VTAM® is still active from your previous definitions such that the IUTIQDxx TRLE was created, recycle VTAM to reuse that set of IQD devices for the new IUTIQ4xx TRLE. For more information about dynamic TRLEs, see Resources automatically activated by VTAM in z/OS Communications Server: SNA Network Implementation Guide.

IPCONFIG
       SOURCEVIPA
     ;
     DEVICE VIPA4811  VIRTUAL  0
     LINK   VIPA4811L VIRTUAL  0    VIPA4811
     ;
     DEVICE IUTIQDFE  MPCIPA   
     LINK   HSINTF1       IPAQIDIO      IUTIQDFE
       IPBCAST
     ;
     HOME
       10.81.1.1      VIPA4811L
       200.16.1.1     HSINTF1
     ;
     PRIMARYINTERFACE HSINTF1
     ;
     BSDROUTINGPARMS TRUE
       VIPA4811L 1492 0 255.255.255.0 0
       HSINTF1   1492 0 255.255.255.0 0
     ENDBSDROUTINGPARMS
     ;
     GATEWAY
       200.16  =  HSINTF1  1492  0
     ;
     START IUTIQDFE

IPCONFIG
       SOURCEVIPA
     ;
     DEVICE VIPA4811  VIRTUAL  0
     LINK   VIPA4811L VIRTUAL  0    VIPA4811
     ;
     ; Converted INTERFACE statement
     ;
     ;   - HSINTF1 is from the LINK statement
     ;   - DEFINE IPAQIDIO is from the LINK statement
     ;   - IPBCAST is from the LINK statement
     ;   - IPADDR 200.16.1.1 is from the HOME list entry, /24 is from the
     ;     BSDROUTINGPARMS entry subnet mask
     ;   - CHPID FE is from the DEVICE statement
     ;   - SOURCEVIPAINTERFACE VIPA4811L is from the order of the HOME list
     ;     entries
     ;
     INTERFACE HSINTF1
       DEFINE IPAQIDIO
       IPADDR 200.16.1.1/24
       CHPID   FE
       SOURCEVIPAINTERFACE VIPA4811L
     ;
     ; HSINTF1 is removed from the HOME list
     ;
     HOME
       10.81.1.1      VIPA4811L
     ;
     PRIMARYINTERFACE HSINTF1 
     ;
     ; HSINTF1 is removed from BSDROUTINGPARMS
     ;
     BSDROUTINGPARMS TRUE
       VIPA4811L 1492 0 255.255.255.0 0
     ENDBSDROUTINGPARMS
     ;
     ; GATEWAY statement is converted to BEGINROUTES
     ;
     BEGINROUTES
       ROUTE 200.16.0.0/16  =  HSINTF1  MTU 1492
     ENDROUTES
     ;
     ; START statement uses the interface name
     ;
     START HSINTF1