Setting up the service machine

Proceed like this to set up the service machine:

1. For each guest that is to have an IUCV connection to the service machine add a home entry, device, link, and start statement to the service machine's PROFILE TCPIP file.
   The statements have the form:

      Home
      	<ip_address1>	<link_name1>
      	<ip_address2>	<link_name2>
       ...
   
      Device <device_name1> IUCV 0 0 <guest_ID1> A
      Link <link_name1> IUCV 0  <device_name1>
   
      Device <device_name2> IUCV 0 0 <guest_ID2> A
      Link <link_name2> IUCV 0  <device_name2>
   
      ...
   
      Start <device_name1>
      Start <device_name2>
      ...

   where

   <ip_address1>, <ip_address2>

   are the IP address the Linux® instances.

   <link_name1>, <link_name2>, ...

   are variables that associate the link statements with the respective home statements.

   <device_name1>, <device_name2>, ...

   are variables that associate the device statements with the respective link statements and start commands.

   <guest_ID1>, <guest_ID1>, ...

   identify the z/VM® guest virtual machines on which the connected Linux instances run.

   In our example, the PROFILE TCPIP entries for our example might look of this form:

      Home
      	1.2.3.4 LNK1
      	1.2.3.5 LNK2
       
      Device DEV1 IUCV 0 0 LNX1 A
      Link LNK1 IUCV 0  DEV1
   
      Device DEV2 IUCV 0 0 LNX2 A
      Link LNK2 IUCV 0  DEV2
   
      Start DEV1
      Start DEV2
      ...

2. Add the necessary z/VM TCP/IP routing statements (BsdRoutingParms or Gateway). Use an MTU size of 9216 and a point-to-point host route (subnet mask 255.255.255.255). If you use dynamic routing, but do not wish to run routed or gated on Linux, update the z/VM ETC GATEWAYS file to include permanent host entries for each Linux instance.
3. Bring these updates online by using OBEYFILE or by recycling TCPIP and/or ROUTED as needed.