Enterprise Extender configuration

Enterprise Extender has a number of key parameter definitions that are required in order to enable Enterprise Extender on z/OS. There are also some optional definitions that might be implemented, depending on an organization's requirements.

There are also definitions required on the SNASw routers, and implementing the definitions is normally a job performed by the network group responsible for looking after the WAN equipment. Though this task is usually not handled by a z/OS network administrator, as with any of the data center network equipment, you need to provide some information in order for the SNASw router to connect to z/OS.

A prerequisite of implementing Enterprise Extender on z/OS is that Communications Server must be APPN-enabled.

TCP/IP profile statements for Enterprise Extender

Assuming that TCP/IP address space is up and running prior to the implementation of EE, the following tasks must be performed in the TCP/IP profile definitions:

Define a static VIPA and assign it an IP address.
Define the IUTSAMEH device.
If, as part of parallel sysplex definitions, you define a distributed VIPA using DYNAMICXCF, then IUTSAMEH is automatically defined.
It is recommend that a dynamic routing protocol, like OMPROUTE, be implemented.
If you are using OMPROUTE, there are additional definitions required, but these are not shown.

Figure 1 illustrates an example of TCP/IP profile statements that are part of the Enterprise Extender definition process. The TCP/IP profile shows device statements for Enterprise Extender, the Enterprise Extender UDP ports, IP address of Enterprise Extender, and start device statement for Enterprise Extender.

The example uses a unique Enterprise Extender VIPA because it provides separation from the IP VIPA and can be monitored independently. Some sites use the IP VIPA as the Enterprise Extender VIPA, as well.

TCP/IP needs a definition for the port represented by the VTAM application (same-host, IUTSAMEH). This must be active before VTAM can establish any Enterprise Extender connections.

Figure 1. TCP/IP profile

;Virtual Device and Link statements
;EE VIPA device
device VIPAEE   virtual 0
link   VLINKEE  virtual 0  VIPAEE
  
;IP VIPA device
device VIPA1   virtual 0
link   VLINK1  virtual 0  VIPA1
  
;There will also be other VIPA device statements for the IP VIPA.
  
;Device statement for OSA device
device OSADEV1 MPCIPA NONROUTER
LINK   OSALNK1 IPAQENET OSADEV1

;Device statement for VTAM EE connection
device IUTSAMEH MPCPTP
link   EELINK   MPCPTP IUTSAMEH

;There will also be other device statements for the interfaces such as OSA.
  
;PORT statements for Enterprise Extender 12000-12004 default ports
12000 UDP NET
12001 UDP NET
12002 UDP NET
12003 UDP NET
12004 UDP NET
  
;Home Statements
10.134.61.188   VLINKEE       ; This is the EE Static VIPA address
10.134.61.180   VLINK1        ; stack IP VIPA precedes 1st physical device
10.140.40.50    OSALNK1
10.144.61.188   EELINK        ; SAMEHOST address for EE connection

;Start device statement 
start OSADEV1      ;Start real interface devices
start IUTSAMEH     ;Start

VTAM statements for Enterprise Extender

Define the Enterprise Extender IP address and TCP name in the VTAM ATCSTRxx configuration list member; see Figure 2. Do this on each of the LPARs that are Enterprise Extender-capable.

Figure 2. VTAM statements for Enterprise Extender (1 of 2)

* SYSP.VTAMLST(ATCSTR01)
* APPN definitions (some of which are mentioned below)

APPNCOS=#CONNECT,
CPCDRSC=YES,
CDSERVR=YES,
CPCP=YES,
CONNTYPE=APPN,
HPR=(RTP,NONE)
NN=YES

* EE specific definitions

IPADDR=10.134.61.188
TCPNAME=TCPIP
  
* External communications adapter (XCA) VTAM major node defines the IP port 
* connection to the z/OS TCP/IP stack that VTAM will use for EE connections
* SYSP.VTAMLST(XCAEE)

XCAEE1          vbuild type=XCA
EEPORT   port   medium=hprip,
                livtime=10,
                iptos=(20,40,80,C0),
                SAPADDR=4,
                srqretry=3,
                srqtime=15
EEGROUP  group  dial=yes
                dynpu=yes,
                DYNPUPFX=EX, 
                AUTOGEN=(nnnn,EEXL,EEXP), 
                call=inout 
  
* VTAM Switched major node definition member for a remote SNA Server node
* SYSP.VTAMLST(SWEEPU1)

SWPU1  VBUILD   TYPE=SWNET
PU1    PU       MAXDATA=1033, 
                ADDR=01, 
                CPNAME=SNASRVR, 
                PUTYPE=2 
  
* VTAM CDRSC definition member for independant LU (LU6.2) on PU1 above.
* SYSP.VTAMLST(CDRS1)
CDRSC1  VBUILD  TYPE=CDRSC

ILU1            CDRSC  ALSLIST=PU1

Figure 3. VTAM statements for Enterprise Extender (2 of 2)

* VTAM Switched major node for CISCO SNASw router 
* The SNASW router definition examples are contained in the next section.
* SYSP.VTAMLST(SWRTR1) 

        VBUILD  TYPE=SWNET 
SNASW1  PU      ADDR=01,
                DISCNT=NO, 
                DYNLU=YES, 
                CPNAME=SNASWR1, 
                CONNTYPE=APPN,CPCP=YES,HPR=YES, 
                PUTYPE=2

Important: We recommend that you use a unique IP VIPA address for Enterprise Extender on each LPAR.