HP-UX SNAplus2 R7 Administration Guide

Configuring APPC Communication
Defining Local LUs
7 Configuring APPC Communication
APPC applications, 5250 emulation programs, and CPI-C applications all require that you configure APPC first. An
APPC application uses the node’s LU type 6.2 resources to communicate with another APPC or CPI-C application
on a host or peer computer, using a specified mode.
If the applications use CPI-C, you may need to do additional CPI-C configuration after configuring APPC. A
CPI-C application uses the node’s LU type 6.2 and mode resources to communicate with another APPC or CPI-C
application on a host or peer computer. You define the same resources for a CPI-C application as for an APPC
application. In addition, if the TP on the SNAplus2 computer is the invoking TP (the TP that starts the conversation),
you may need to define one or more side information entries for it, as described in Section 7.6,
Defining CPI-C
Side Information. Each of these entries provides information on a partner TP, the LU and mode resources used to
access it, and any security information required.
The configuration steps for APPC depend on whether the LU 6.2 traffic is dependent or independent. Unless the
remote node is a host, you must use independent traffic. If the remote node is a host, you can use either dependent
or independent traffic.
Before you can configure APPC communication, you must perform the following configuration:
• Configure the node as described in Section 4.2, Configuring the Node.
• Configure connectivity as described in Chapter 5, Defining Connectivity Components.
Note
In an APPN network, a single link station to an adjacent network node can be used to
communicate with any remote node in the network, so you do not need to configure a
separate link station to each remote node.
In many cases, APPC applications can use the control point LU on both the local and remote nodes, and a standard
mode. In this case, your configuration is ready for APPC without any further configuration.
The following steps can be used to configure APPC communication on the local node. Depending on the types of
the local and remote nodes, and on your application, you may not need to perform these steps.
1. Define a local LU as described in Section 7.1, Defining Local LUs.
2. Define a remote node as described in Section 7.2, Defining Remote Nodes.
3. Define a partner LU as described in Section 7.3, Defining Partner LUs.
4. Define an invokable TP as described in Section 7.4, Defining TPs.
5. Define a mode as described in Section 7.5, Defining Modes and Classes of Service.
6. Define CPI-C side information as described in Section 7.6, Defining CPI-C Side Information.
7. Define APPC security as described in Section 7.7, Configuring APPC Security.
8. To configure 5250 communication, see Chapter 8, Configuring User Applications.
7.1 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
104