Defining Connectivity Components

Defining Link Stations

Parameters for Independent LU Traffic

You need the following information to configure this link station for use by independent LUs (LUs of type 6.2 for use by APPC, 5250, or CPI-C applications):

Remote node name

The fully qualified CP name of the remote node.

If the remote system is a VTAM host, you can find the network name (the first eight characters of the fully qualified name) in the NETID parameter of the VTAM Start command. The last eight characters are in the SSCPNAME parameter of the VTAM Start command.

If you enter the name of a new remote node, you can add a definition for the remote node to enable you to define partner LUs on the new remote node.

To define a new remote node in this way, specify the remote node type for this definition rather than specifying a remote node type of Discover. (If the local node is a LEN node, you do not need to specify the remote node type, and the Remote node type field does not apply.) If the local node is an end node rather than a LEN node, and if you specify a remote node type of Discover, you do not have to supply the remote node name. If you do not supply a remote node name, any adjacent node can use the link station.

Alternatively, you can specify Discover dynamically. This leaves the remote node name empty and sets the remote node type to Discover, so that any adjacent node can use the link station. The Discover dynamically option is not available if the local node is a LEN node.

Remote node type

The level of APPN support on the remote node that is accessed through this link station (only applicable if the local node is an end node).

If you do not know whether the remote node is a LEN node or end node or whether it is a network node, you can choose Discover. Discovering the level of APPN support on the remote node can delay link activation

Chapter 5

161