Configuring TCP/IP and VTAM for HPR/IP

The following TCP/IP and VTAM changes are needed to support HPR/IP (Enterprise Extender) connections. This procedure assumes you have z/OS and hardware on the mainframe to support Ethernet connections. These host changes are one time changes to your TCP/IP profile, VTAM startup, and XCA major node.

  1. Configure TCP/IP

  2. Configure VTAM

See also:

Configure TCP/IP

Define the VIPA device. When you configure RJE or NJE, this will match the Host name or IP address entered on the Link tab.

IPCONFIG SOURCEVIPA               
;*******************************  
; VTAM to TCPIP Stack             
;*******************************  
DEVICE IUTSAMEH MPCPTP            
LINK EELINK MPCPTP IUTSAMEH       
HOME                              
10.1.1.205  EELINK            
START IUTSAMEH                    
;*******************************  
; Enterprise Extender VIPA        
;*******************************  
DEVICE VIPA01 VIRTUAL 0           
LINK LVIPA1   VIRTUAL 0  VIPA01   
HOME                              
10.1.1.204  LVIPA1            

Top

Configure VTAM

Specify the NETID. When you configure RJE or NJE, this will match the NETID entered on the Link tab.

SSCPID=06,NOPROMPT,              
CONFIG=02,MAXSUBA=31,SUPP=NOSUP,
SSCPNAME=BAR6CDRM,               
NETID=BARRSYS,                   
TCPNAME=TCPIP      

X
X
X
X
 

Setup a major node for the XCA. Only one XCA definition with a Medium=HPRIP is allowed for a given VTAM. XCA connections are used as the path to connect the remote Enterprise Extender node to VTAM. You can use Autogen to create dynamic PU’s for each connection.

***********************************************************
*                                                          
* NAME: XCAEE  XCA MAJOR NODE FOR HOST Enterprise Extender
*                                                          
***********************************************************

XCAEE

VBUILD

TYPE=XCA

 

PORT9E

PORT

MEDIUM=HPRIP,

X

 

 

SAPADDR=4,VNGROUP=GPEAA,    

X

 

 

VNNAME=BARRSYS.VNEE6         

 

*

 

 

 

GPEAA

GROUP

DIAL=YES,      

X

 

 

ISTATUS=ACTIVE,

X

 

 

CALL=INOUT,

X

 

 

AUTOGEN=(10,V,P)

 

PC

PU ADDR=01,ANS=CONT,DISCNT=NO,IRETRY=YES,CPCP=YES,

-00250019

 

MAXDATA=1456,MAXOUT=7,PASSLIM=7,PUTYPE=2

00260020

  1. If you are NOT using Autogen, define a switched Major Node with PU’s for each RJE or NJE that will be connecting using CP – CP sessions. When you configure RJE or NJE, this will match the CPNAME entered on the Link tab.

Because the sample VBUILD does not include a group, the XCA’s group is applied at connection initialization.

********************************************    
*                                               
* NAME: SMN for EE connection using static PU's
*                                               
********************************************    
*                                               

EESMNMD

VBUILD

TYPE=SWNET,MAXNO=256,MAXGRP=256  

 

TSPMN1

PU

MAXPATH=5,MAXDATA=1490,ADDR=01,   

X

 

 

CPNAME=CPTSPMN1,

X

 

 

CPCP=YES,HPR=YES,

X

 

 

PUTYPE=2

 

Top