HP-UX SNAplus2 R7 Administration Guide

Introduction to SNAplus2
SNAplus2 Components
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 Section 7.4,
Defining TPs.
• If the TP is operator-started (not started automatically by SNAplus2), and the use of the TP does not need to
be restricted, you do not need to define any additional resources. The only exceptions are when you want to do
the following:
• Change the default timeout for a RECEIVE_ALLOCATE issued by the TP.
• Specify that the TP is a broadcast queued TP (which means that incoming conversation requests can be
routed dynamically to the TP wherever it is running).
For more information about TP configuration, see Section 7.4, Defining TPs.
For more information about the APPC API, refer to HP-UX SNAplus2 APPC Programmer’s Guide.
CPI-C API
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, as described in Section 2.3.3, Application Programming Interfaces.
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. Each of these entries provides information about a partner
TP, the LU and mode resources used to access the partner TP, and any security information required.
For more information, refer to HP-UX SNAplus2 CPI-C Programmer’s Guide.
CSV API
The Common Service Verb (CSV) API provides utility verbs that enable an application program to perform functions
such as character set conversion and trace file control.
For more information, refer to HP-UX SNAplus2 CSV Programmer’s Guide.
HLLAPI
HLLAPI (high-level language application programming interface) enables applications that use the SNAplus2 3270
emulator program to communicate with a host.
For more information, refer to HP-UX SNAplus2/TN3270 HLLAPI Programmer’s Guide or HP-UX SNAplus2 3270
User’s Guide.
LUA API
The LUA API enables application programmers to write applications that communicate with host applications at
the request unit and response unit (RU) level, and to send and receive data on both the SSCP-LU session and the
PLU-SLU session. This API can be used to support LU 0, 1, 2, or 3 communication with the host.
An LUA application uses the node’s LU type 0–3 resources to communicate with a host application. You do not
need to define any additional resources.
For more information, refer to HP-UX SNAplus2 LUA Programmer’s Guide.
50