Step 1: Prepare your TCP/IP configuration

Procedure

Reserve the UDP ports for EE using the PORTRANGE statement or PORT statements to prevent another application from using one of the EE ports.
Tip:
- If you do not reserve the UDP ports, you might have a conflict when another application uses the port. For example:
```
      PORTRANGE                          
     12000 5 UDP NET  ; RESERVE UDP PORTS 12000-12004 FOR EE
```
- Use the MVS™ job name associated with the VTAM® started task to reserve UDP ports that are to be used for EE network connections. The MVS job name for a given started task can be assigned based on various inputs. These inputs are examined in the following order:
  1. The job name specified in the JOBNAME= parameter or the identifier specified on the MVS START command. In the PORTRANGE example, VTAM was started with an identifier of NET and therefore the job name specified was NET.
  2. The job name specified on the JOB JCL statement within the member.
  3. The member name.
Note: You cannot use wildcard characters when you specify the VTAM job name for EE UDP port reservations on either the PORT statements or PORTRANGE statement.
Evaluate your IP routing environment. See Static VIPA considerations for more information. Also identify the number of static VIPAs.
Define one or more static VIPAs for the EE connection. The following are the TCP/IP profile requirements for Enterprise Extender:
- For IPv4, define the static VIPA addresses for EE by using the DEVICE, LINK, and HOME statements. The following example defines two local static IPv4 VIPA addresses for EE:
```
;********************************
; Enterprise Extender VIPAs, IPv4
;********************************
DEVICE VIPA01 VIRTUAL 0
LINK LVIPA1 VIRTUAL 0 VIPA01
DEVICE VIPA02 VIRTUAL 0
LINK LVIPA2 VIRTUAL 0 VIPA02
HOME
  92.1.1.1 LVIPA1
  92.1.1.2 LVIPA2
```
- For IPv6, define the static VIPA addresses for EE by using the INTERFACE statement. The following example defines one static IPv6 VIPA address for EE:
```
;*******************************
; Enterprise Extender VIPA, IPv6
;*******************************
INTERFACE VIPA6 DEFINE VIRTUAL6 IPADDR 2001:0db8::91:1:1:2
```
- Optionally, enable SOURCEVIPA. The EE static VIPA is used as the source IP address for all EE traffic, regardless of the SOURCEVIPA setting. EE uses the static VIPA as the source IP address in all outbound traffic regardless of the SOURCEVIPA setting. If you have NOSOURCEVIPA coded or defaulted, non-EE traffic uses the outbound interface address as the source IP address but EE traffic still uses the static VIPA as the source IP address.
Define IUTSAMEH connectivity either by using DYNAMICXCF or by creating manual IUTSAMEH definitions in the TCP/IP profile.
If you configure manual IUTSAMEH definitions and also configure the DYNAMICXCF definition, the manual IUTSAMEH definitions will coexist with the other connectivity (XCF and HiperSockets™) definitions that dynamic XCF can generate.
To dynamically configure IUTSAMEH, do the following step:
- IUTSAMEH definitions are dynamically defined when dynamic XCF support is enabled using IPCONFIG DYNAMICXCF or IPCONFIG6 DYNAMICXCF. For IPv4, the device name is IUTSAMEH and the link name is EZASAMEMVS. For IPv6, the interface name is EZ6SAMEMVS.
To manually configure IUTSAMEH definitions, do the following step:
- For IPv4, define and start IUTSAMEH using the DEVICE, LINK, HOME, and START statements.
- For IPv6, define and start IUTSAMEH using the INTERFACE and START statements.
Following is an example of a manual configuration:
```
;*******************************
; VTAM to TCPIP Stack, IPv4
;*******************************
DEVICE IUTSAMEH MPCPTP
LINK EELINK MPCPTP IUTSAMEH
HOME 93.1.1.1 EELINK
START IUTSAMEH


; ******************************
; VTAM to TCPIP Stack, IPv6
; ******************************
INTERFACE EELINK6 DEFINE MPCPTP6
   TRLENAME IUTSAMEH
   IPADDR 2001:0db8::91:1:1:1 
START EELINK6
```
Note: If you choose to manually configure the IUTSAMEH connections and the IP address is used only for EE, you do not have to specify the IP address for IUTSAMEH. Warning messages can be ignored.

Tip: To simplify EE definitions, consider defining IUTSAMEH connections using the IPCONFIG DYNAMICXCF statement for IPv4 and the IPCONFIG6 DYNAMICXCF statement for IPv6.