HP-UX SNAplus2 R7 Administration Guide

Introduction to SNAplus2

SNAplus2 Components

MS API

The Management Services (MS) API enables an application to communicate with other MS products in an APPN

network. An application can be either NMVT-level or MDS-level, depending on the type of MS data it sends and

receives. SNAplus2 performs any data conversion that is required.

For more information, refer to

HP-UX SNAplus2 MS Programmer’s Guide.

NOF API

The NOF API can be used to write applications that administer SNAplus2 conﬁguration and management resources.

For more information, refer to HP-UX SNAplus2 NOF Programmer’s Guide.

Windows APIs

WINDOWS

The SNAplus2 client software includes API libraries that are fully compatible with Microsoft Host Integration Server

and the Windows Open Systems Architecture (WOSA), enabling applications written for Host Integration Server to

run unchanged on the SNAplus2 Windows client.

SNAplus2 supports the following WOSA APIs:

• Windows APPC

• Windows CPI-C

• Windows LUA

• Windows CSV

• 3270 Emulator Interface Speciﬁcation

In addition, SNAplus2 supports the proprietary NOF API for client applications on Windows that conﬁgure and

manage SNAplus2 resources.

For more information about Windows SNA APIs, see the SNAplus2 API manuals (which contain information about

the Windows APIs as well as the HP-UX APIs).

2.3.4 Client/Server Support

Computers running SNAplus2 can be conﬁgured to communicate using client/server protocols. When client/server

protocols are used in a network, all the computers using client/server protocols to communicate in that network

are referred to as a domain. Each computer in the network speciﬁes the same domain name when SNAplus2 is

installed.

The computers running SNAplus2 in a client/server conﬁguration can take the following roles:

• A server contains an SNA node and its associated connectivity components. The server provides SNA

connectivity to applications on the local system or on other machines in the same domain.

• A client does not contain SNA components, but accesses them through a server. It can access one or more

servers at the same time, and can run concurrent applications as needed.

Servers must be HP-UX computers; clients can be running HP-UXor Windows. (A HP-UX computer can be either

a server or a client, but not both; you cannot install both the server and the client on the same computer.) Servers

and clients communicate across the SNAplus2 domain using TCP/IP.

You can conﬁgure one or more separate SNAplus2 domains on the same physical network, using a unique name

for each different domain. Use the same domain name for all SNAplus2 servers and clients that belong the same

domain. A single SNAplus2 domain can correspond to a TCP/IP subnet, can be part of a TCP/IP subnet (so that

there are two or more separate SNAplus2 domains in the same subnet), or can span multiple subnets.