z/OS Communications Server: SNA Network Implementation Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Activating EE

z/OS Communications Server: SNA Network Implementation Guide
SC27-3672-01

After you have done the preparation work, you can activate EE to receive benefits provided by EE.

Before you begin

Define static VIPAs to be used for EE connections, start the TCP/IP stack enabled for EE, and activate IUTSAMEH by static definition or by specifying DYNAMICXCF. See Step 1: Prepare your TCP/IP configuration for more information about preparing your TCP/IP configuration.

Procedure

Perform the following steps to start EE:

  1. Enable z/OS® Communications Server to accept or initiate EE connections by activating the EE XCA major node:
    • The first line activated in the EE XCA major node establishes a VTAM® connection to the TCP/IP stack supporting Enterprise Extender. When this communication is established, the following messages appear on the console:
      EZZ4313I INITIALIZATION COMPLETE FOR DEVICE IUTSAMEH       
      EZZ4324I CONNECTION TO 9.67.1.3 ACTIVE FOR DEVICE IUTSAMEH
    • For the first line activation associated with each unique static VIPA address (IPADDR or HOSTNAME), VTAM registers this VIPA address with the TCP/IP stack for EE communications. Any other line you activate from a group results in a new message that indicates VIPA activation. The following message appears on the console:
      EZZ4324I CONNECTION TO 9.67.1.5 ACTIVE FOR DEVICE IUTSAMEH
      EZZ4324I CONNECTION TO 9.67.1.7 ACTIVE FOR DEVICE IUTSAMEH

      Each message signifies that EE is registering the new static VIPA address with the TCP/IP stack and that the VIPA is ready to use.

  2. Establish outbound EE connections by configuring a predefined EE network. Perform the following actions:
    • Activate the EE switched major node.
    • Dial the associated switched PU.
         V NET,DIAL,ID=SWIP2A1       
                                          
      	   IST097I VARY ACCEPTED                                           
      	   IST590I CONNECTOUT ESTABLISHED FOR PU SWIP2A1 ON LINE LNIP1     
      	   IST1086I APPN CONNECTION FOR NETA.SSCP2A IS ACTIVE - TGN = 21   
      	   IST241I VARY DIAL COMMAND COMPLETE FOR SWIP2A1                  
      	   IST1488I ACTIVATION OF RTP CNR00002 AS PASSIVE TO NETA.SSCP2A   
      	   IST1488I ACTIVATION OF RTP CNR00001 AS ACTIVE TO NETA.SSCP2A    
      	   IST1096I CP-CP SESSIONS WITH NETA.SSCP2A ACTIVATED

      If the partner is ready to accept connections, connections will be established. To establish connections using EE connection network, see Configuring the EE connection network.

  3. Accept inbound EE connections by activating a switched PU to receive inbound connections. Use one of the following methods to identify the switched PU that will receive the EE connection.
    • Activate a switched PU to receive the incoming connection.
    • Specify DYNPU=YES on a GROUP within the XCA major node to indicate that a dynamic PU should be created when inbound connections arrive. Optionally, specify a model to be used for creation of dynamic physical units for incoming calls by activating a model major node containing a PU statement with DYNTYPE=EE specified.

Results

Activating EE automatically:

If you want to automate EE activation and connection to EE partners with minimal operator intervention, specify the EE XCA major node and any related EE switched major nodes in the VTAM configuration start list (ATCCONxx). Specifying DWACT=YES on the switched PU causes VTAM to automatically dial the switched PU upon activation.

Tip: The connection attempt might initially fail. Consider coding REDIAL and REDDELAY on the switched path definition statement. For more information about path definition statements see z/OS Communications Server: SNA Resource Definition Reference. For EE to automatically recover after a connection loss, consider coding DWINOP on the switched PU.
Guideline: Use caution if both EE endpoints support DWINOP. See Dial usability - DWACT, DWINOP, KEEPACT, REDIAL, and REDDELAY for more information.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014