MAINFRAME > Administrator > Performance

Implement HiperSockets Communication With IBM Enterprise Extender

HiperSockets Enterprise Extender

In my previous work I was a mainframe communication system programmer supporting multiple clients. I did a HiperSockets implementation for overcoming the difficulty of maintaining the old VTAM SUBAREA channel-to-channel connectivity and to get a latency. HiperSockets gave us the opportunity of establishing the LPAR intraconnectivity within the sysplex with the ease of maintaining the definition. This also becomes easier to recover LPAR connectivity in the disaster recovery site with just few definitions in place.

We adopted HiperSockets communication directly as a visible HiperSockets interface over IBM Enterprise Extender (EE). There were many considerations before starting with this definition, since our environment was having dynamic routing (OMPROUTE). Keeping the routing safe without disturbing the existing connection was a challenge. The definition in this article explains how two LPARS in the sysplex would show the HiperSockets communication over IBM EE.

Definitions to Make it Work

First we defined the HiperSockets channel, Control unit and Device using Hardware Configuration Definition. So we defined CHPID with 0F and 16 Channel with EEF0-EEFF. We selected internal IP address value of 10.1.7.1 For LPARA and 10.1.7.2 for LPARB. It’s important to ensure the IBM EE is implemented across the LPAR to support HiperSockets communication. The TCPIP profile definition for TCP/IP stack running on LPARA is:

UNDER THE TCPIP PROFILE : TCPIP1.LPARA.PARMLIB(PROFILE)

Interface statement for HIPERSOCKETS is:

INTERFACE HIPERL0F    
   DEFINE  IPAQIDIO   
   CHPID 0F           
   IPADDR  10.1.7.1/24

The EE VIPA for HIPERSOCKETS IP ranges are:

DEVICE VIPA01 VIRTUAL 0     
LINK LVIPA1 VIRTUAL 0 VIPA01

From there, add the EE VIPA IP address under HOME Statement:

10.1.7.11        LVIPA1          ; HIPERSOCKETS FOR LPARA

Next, add the Start command for HIPERL0F:

START HIPERL0F

To OMPRCONF member at TCPIP1.LPARA.PARMLIB(OMPRCONF), change to:

GLOBAL_OPTIONS IGNORE_UNDEFINED_INTERFACES=YES;
Please perform the below changes to VTAM under SYS1.VTAMLST

Add the SWITCH node definition to have IBM EE HiperSockets communication for LPARA speaking to LPARB:

MEMBER NAME : SWEEIAIB
****** ***************************** Top of Data ******************************
000001 *********************************************************************   
000002 * SW NODE DEFINITION FOR ENTERPRISE EXTENDER SUPPORT ON LPAR A TO LPAR B         
000003 * HIPERSOCKETS                                                           
000004 * CONTACT : JAGADISHAN                                   
000005 *********************************************************************   
000006          VBUILD TYPE=SWNET                                              
000007 EEIAIBP  PU    ADDR=21,                                                X
000008                DISCNT=NO,                                              X
000009                CPNAME=Z0S002,                                          X
000010                NETID=ISIMD000,                                         X
000011                CONNTYPE=APPN,                                          X
000012                CPCP=YES,                                               X
000013                PUTYPE=2,                                               X
000014                DWACT=YES,                                              X
000015                DYNLU=YES,                                              X
000016                HPR=YES,                                                X
000017                DWINOP=YES,                                             X
000018                TGP=EEXTCAMP                                             
000019 *              STATOPT='EE TO LPAR B'                                     
000020          PATH  IPADDR=10.1.7.12,                                       X
000021                REDIAL=FOREVER,                                         X
000022                SAPADDR=8,                                              X
000023                GRPNM=GRPEE2                                             

Add the second group to the external communication adapter (XCA) node to address the EE VIPA address:

SYS1.VTAMLST
MEMBER NAME : XCAEEIA
000001 *********************************************************************   
000002 * XCA DEFINITION FOR ENTERPRISE EXTENDER SUPPORT ON LPAR A                
000003 *********************************************************************   
000004          VBUILD TYPE=XCA                                                
000005 PORTEE   PORT  MEDIUM=HPRIP,                                           X
000006                SAPADDR=4,                                              X
000007                LIVTIME=15,                                             X
000008                SRQTIME=15,                                             X
000009                SRQRETRY=9                                               
000010 *              STATOPT='EE XCA PORT'                                    
000011 GRPEE    GROUP DIAL=YES,                                               X
000012                AUTOGEN=(25,EELN,EEPU),                                 X
000013                IPADDR=xxx.xxx.xxx.x,                                    X
000014                DYNPU=NO,                                               X
000015                CALL=INOUT,                                             X
000016                ISTATUS=ACTIVE                                           
000017 *                                                                       
000018 GRPEE2   GROUP DIAL=YES,                                               X
000019                AUTOGEN=(25,EELN1,EEPU1),                               X
000020                IPADDR=10.1.7.11,                                       X
000021                UPARM1=0,                                               X
000022                DYNPU=NO,                                               X
000023                CALL=INOUT,                                             X
000024                ISTATUS=ACTIVE    



Like what you just read? To receive technical tips and articles directly in your inbox twice per month, sign up for the EXTRA e-newsletter here.


comments powered by Disqus

Advertisement

Advertisement

2017 Solutions Edition

A Comprehensive Online Buyer's Guide to Solutions, Services and Education.

IBM Systems Magazine Subscribe Box Read Now Link Subscribe Now Link iPad App Google Play Store
Mainframe News Sign Up Today! Past News Letters