|
|
|
|
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 SNAP-IX 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 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 Configuring the Node.
Configure connectivity as described in Defining Connectivity Components.
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.
Define a local LU as described in Defining Local LUs.
Define a remote node as described in Defining Remote Nodes.
Define a partner LU as described in Defining Partner LUs.
Define an invokable TP as described in Defining TPs.
Define a mode as described in Defining Modes and Classes of Service.
Define CPI-C side information as described in Defining CPI-C Side Information.
Define APPC security as described in Configuring APPC Security.
To configure 5250 communication, see Configuring User Applications.
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 SNAP-IX node is an end node or network 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:
Select APPC and either New independent local LU or New dependent local LU from the Services menu on the Node window.
Issue the following command:
define_local_lu
You can use the advanced dialog to specify sync point support, attach routing characteristics, whether password substitution should be used, restrictions on SSCP access, and security.
The following parameters are required for local LU configuration:
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.
The LU alias of the LU. If you do not enter an alias, the LU name is used as the alias.
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.)
The LU number of the dependent LU. (This field applies only if the LU is a dependent LU.)
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.
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 Configuring User Applications.
|
|
|
 |
|