HP-UX SNAplus2 R7 Administration Guide

Introduction to SNAplus2

SNAplus2 Components

Refer to HP-UX SNAplus2 RJE User’s Guide for information about using RJE to submit jobs to a host and about

setting up the workstation style ﬁle.

APPC Application Suite

SNAplus2 includes the IBM APPC Application Suite, which provides the following set of APPC applications using

independent LU 6.2: ACOPY, AFTP, ANAME, APING, APPC Remote EXECution (AREXEC), and APPC Tell

(ATELL). For more information, refer to HP-UX SNAplus2 APPC Application Suite User’s Guide.

2.3.3 Application Programming Interfaces

SNAplus2 provides several standard programming interfaces that you can use to develop application programs:

• APPC API for peer-to-peer communications between application programs (see Section 2.3.3, Application

Programming Interfaces).

• CPI-C (Common Programming Interface for Communications) for platform-independent communication using

independent LU 6.2 (see Section 2.3.3, Application Programming Interfaces).

• CSV (Common Service Verb) API for utility functions such as character translation and application trace control

(see Section 2.3.3, Application Programming Interfaces).

• HLLAPI (high-level language application programming interface) for application programs that interact with

the 3270 emulation program to automate standard 3270 tasks (see Section 2.3.3, Application Programming

Interfaces).

• LUA API for communications with host applications (see Section 2.3.3, Application Programming Interfaces).

In addition, SNAplus2 includes the following proprietary programming interfaces:

• MS (Management Services) API for network messaging functions (see Section 2.3.3, Application Programming

Interfaces).

• NOF (Node Operator Facility) API for applications that conﬁgure and manage SNAplus2 resources (see Section

2.3.3, Application Programming Interfaces).

•

WINDOWS

Windows client APIs (see Section 2.3.3, Application Programming Interfaces).

For more detailed information about an API, refer to the programming guide for the API (see Related Publications).

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 speciﬁed 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 deﬁne

directory entries for the remote node and its LUs.

• If the TP speciﬁes its local APPC LU using an LU alias, you need to deﬁne the partner LU in order to associate

this alias with a fully qualiﬁed LU name.

• If the TP uses a dependent local LU to communicate with a host, you need a partner LU deﬁnition on the local

node that speciﬁes 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.