gtpc1m20Transmission Control Protocol/Internet Protocol

OSA-Express Connections

You must define an OSA-Express card to the processor and also define an OSA-Express connection to the TPF system before you can use OSA-Express support.

Defining OSA-Express Cards to the Processor

Each OSA-Express card is defined to the processor in the Input/Output Configuration Program (IOCP) and includes the following information:

The following example shows the IOCP definitions for an OSA-Express card that is shared by three LPARs called TPFTEST, TPFPROD, and MVS1. Each of these LPARs can use SDAs E00 to E4F for connections to the card.

CHPID PATH=F9,TYPE=OSD,SHARED,PARTITION=(TPFTEST,TPFPROD,MVS1)
 
CNTLUNIT CUNUMBR=F900,UNIT=OSA,PATH=(F9)
 
IODEVICE UNIT=OSA,ADDRESS=(E00,080),CUNUMBR=F900,UNITADD=00,
          PARTITION=(TPFTEST,TPFPROD,MVS1) 
Note:
You must code TYPE=OSD on the CHPID statement to use OSA-Express support on the TPF system.

Defining OSA-Express Connections to TPF

An OSA-Express connection is defined by entering the ZOSAE command with the DEFINE and OSA parameters specified. The name of the OSA-Express connection must not have been previously defined to this processor.

Because of the number of parameters needed for OSA-Express, some are defined to the processor by first entering the ZOSAE command with the DEFINE parameter specified, while others are defined with subsequent entries of the ZOSAE command with the MODIFY parameter specified.

By entering the ZOSAE command with the MODIFY parameter specified, you can also change existing definitions. With the following exceptions, the OSA-Express connection must not be active when changing existing definitions:

Activating and Deactivating OSA-Express Connections

An OSA-Express connection is activated by entering the ZTTCP command with the ACTIVATE parameter specified. It takes at least 16 seconds for the activation process between the host and the OSA-Express card to be completed. This activation includes registering the real OSA IP address and any VIPAs defined to this OSA-Express connection. When the host registers its IP addresses, the OSA-Express card verifies that the real OSA IP address is unique in the network.

Activate alternate OSA-Express connections the same way before they are needed. If you do not have an active alternate OSA-Express connection and your primary OSA-Express connection fails, network traffic will be delayed for the additional 16 seconds or more it takes for the activation of the alternate OSA-Express connection to be completed. The TPF system does not automatically activate an alternate OSA-Express connection if an OSA-Express connection fails.

An OSA-Express connection can be deactivated manually by entering the ZTTCP command with the INACTIVATE parameter specified. If you enter the ZTTCP command with either the ACTIVATE or INACTIVATE parameter specified, you can specify either one connection or all connections. If you manually deactivate a connection, TPF does not swing the VIPAs to the alternate connection.

Displaying OSA-Express Connections

To display OSA-Express connections, do one of the following:

Deleting OSA-Express Connections

An OSA-Express connection is deleted by entering the ZOSAE command with the DELETE parameter specified when the OSA-Express connection is in an inactive state. The primary OSA-Express connection cannot be deleted if there is an alternate OSA-Express connection defined for it; you must delete the definition of the alternate connection before you delete the primary connection.

Deleting an OSA-Express connection deletes all the VIPAs associated with it. See TPF Operations for more information about the ZOSAE command.