82
Chapter 2
Introduction to SNAplus2
SNAplus2 Components
APPC API
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. The APPC API includes TP server
support, enabling applications to have greater control over starting
transaction programs (TPs) and distributing conversations to those TPs.
If the TP on the SNAplus2 computer is the invoking TP (the TP that
starts the APPC conversation), the additional node resources required
depend on the APPC features used by the TP, and on the type of remote
system it is communicating with:
• If the local node or the remote system with which the TP
communicates is a LEN node, you need to define directory entries for
the remote node and its LUs.
• If the TP specifies its local APPC LU using an LU alias, you need to
define the partner LU in order to associate this alias with a fully
qualified LU name.
• If the TP uses a dependent local LU to communicate with a host, you
need a partner LU definition on the local node that specifies the
uninterpreted name for the LU on the host. When the TP requests a
conversation from the local LU, the local LU sends the host a session
initialization request that contains the uninterpreted name for the
host LU.
In the Motif administration program, directory entries and partner LUs
are not shown explicitly, but are included under the “Remote Systems”
heading in the Node window for the local node.
If the TP on the SNAplus2 computer is the invoked TP (the TP that
accepts a conversation started by the invoking TP), the additional
resources required depend on the APPC features used by the TP, and on
how it is to be started:
• To restrict the TP to using particular options for conversation
security, confirm synchronization, or conversation type (mapped or
basic), or to restrict the number of instances of the TP that can be
running at any time, you must define the TP as a node resource.
• To start the TP automatically when another TP requests a
conversation with it, you must provide the information that
SNAplus2 needs to start the TP. For more information, see Chapter 7,
“Configuring APPC Communication.”
Summary of Contents for HP-UX SNAplus2
Page 4: ...4 ...
Page 14: ...14 Contents ...
Page 22: ...22 ...
Page 23: ...23 1 SNA Terms and Concepts ...
Page 65: ...65 2 Introduction to SNAplus2 ...
Page 107: ...107 3 Administering SNAplus2 ...
Page 132: ...132 Chapter3 Administering SNAplus2 Using the Command Line Administration Program ...
Page 133: ...133 4 Basic Configuration Tasks ...
Page 142: ...142 Chapter4 Basic Configuration Tasks Configuring Logging ...
Page 143: ...143 5 Defining Connectivity Components ...
Page 167: ...167 6 Configuring Dependent LUs ...
Page 174: ...174 Chapter6 Configuring Dependent LUs Defining LU Pools ...
Page 175: ...175 7 Configuring APPC Communication ...
Page 208: ...208 Chapter7 Configuring APPC Communication Configuring APPC Security ...
Page 209: ...209 8 Configuring User Applications ...
Page 222: ...222 Chapter8 Configuring User Applications Configuring RJE Workstations ...
Page 223: ...223 9 Configuring Passthrough Services ...
Page 235: ...235 10 Managing SNAplus2 from NetView ...
Page 248: ...248 Chapter10 Managing SNAplus2 from NetView Using UCF ...
Page 249: ...249 11 Managing SNAplus2 Clients ...
Page 300: ...300 Chapter11 Managing SNAplus2 Clients Managing HP UX Clients ...
Page 301: ...301 A Configuration Planning Worksheets ...
Page 337: ...337 B APPN Network Management Using the Simple Network Management Protocol ...
Page 343: ...343 C Configuring an Invokable TP Using snaptpinstall ...
Page 353: ...353 D Using SNAplus2 in a High Availability Environment ...