Defining Local LUs

In many cases, applications can use the local node's control point LU, which is automatically defined when you configure the node. This is the default LU—if your application does not specify a particular LU, it can use this one. If the application uses the default LU, you do not need to define a local LU. Check the documentation for your APPC application, or contact the application programmer.

If you are configuring dependent LUs of type 6.2 for use with APPC or CPI-C applications, you may wish to define them as members of the default pool. An application that does not specify a particular local LU is assigned an unused LU from the pool of LUs defined as default LUs.

You can define dependent LU 6.2s as default LUs (and you can define default LUs on more than node). An application requesting a default LU can be assigned to any of these LUs as available; the LU does not have to be on the same computer as the application. However, if you are defining partner LUs for the applications, the partner LUs must be defined on all nodes where default LUs are defined, so that the application can contact the correct partner LU using any of the default local LUs defined on any node.

Independent APPC and 5250 use independent LUs. Each LU-LU session involves a local LU and a partner LU. For the local LU, you can use the predefined default LU associated with the node control point, or you can configure new local LUs. The partner LU need not be configured at all if the SNAplus2 node is an end node in an APPN network, because APPN can locate partner LUs dynamically. However, you do have to configure the partner LU if your network is not an APPN network or if the node is a LEN node. In this case, you must configure the remote node where the partner LU resides, then define the partner LU on the remote node. (If the partner LU is the default LU on the remote node, you do not need to define it explicitly because it is added automatically when you define the remote node.)

To configure an APPC local LU, use one of the following methods:

You can use the advanced dialog to specify sync point support, attach routing characteristics, restrictions on SSCP access, and security.

Local LU Configuration Parameters

The following parameters are required for local LU configuration:

LU name

The LU name of the local LU.

If you do not know what name to use, consult your SNA network planner.

This LU name is the second part of the fully qualified LU name of the local LU. The first part of the fully qualified LU name (the network name) is always the same as the first part of the CP name of the local node.

LU alias

The LU alias of the LU. If you do not enter an alias, the LU name is used as the alias.

Host LS/DLUR PU

The name of the host link station or DLUR PU to which the LU belongs. (This field applies only if the LU is a dependent LU.)

LU number

The LU number of the dependent LU. (This field applies only if the LU is a dependent LU.)

Member of default pool

Whether to make the LU a member of the default dependent APPC LU pool. An application that does not specify a particular local LU to use is assigned an available LU from the default pool.

This field applies only if the LU is a dependent LU.

Additional Configuration

After performing the local LU configuration, continue with the following configuration tasks:

• To define a remote node, see “Defining Remote Nodes”.

• To define a partner LU, see “Defining Partner LUs”.

• To define an invokable TP, see “Defining TPs”.

• To define a mode, see “Defining Modes and Classes of Service”.

• To define CPI-C side information, see “Defining CPI-C Side Information”.

• To define APPC security, see “Configuring APPC Security”.

• To configure 5250 communication, see Chapter 8 “Configuring User Applications”.