HP SNA Application Programming Interface for OpenVMS

Software
Product
Description
PRODUCT NAME: HP SNA Application Programming SPD 26.86.10
Interface for OpenVMS, Version 2.7
This SPD describes HP SNA Application Programming
Interface for OpenVMS, which is available for the Open-
VMS I64, OpenVMS Alpha and OpenVMS VAX plat-
forms. All information applies to all platforms unless
otherwise indicated.
DESCRIPTION
The HP SNA Application Programming Interface for
OpenVMS (API) is a layered software product that al-
lows user-written applications running on suitably con-
gured OpenVMS systems within a DECnet or TCP/IP
network or on suitably congured OpenVMS systems
within an OpenVMS SNA environment to exchange in-
formation with cooperating applications on an IBM host.
The API software exists in the OpenVMS system as a
shareable image. Access between the cooperating HP
and IBM applications is via one of the following SNA
server or gateway products:
TCP/IP or DECnet Connections
HP SNA Peer Server
HP SNA Domain Gateway
HP SNA Access Server for Windows NT®
HP SNA Server for OpenVMS Alpha, a layered prod-
uct that supports local access as well as TCP/IP and
DECnet clients
DECnet Only Connections
HP DECnet SNA Gateway for Synchronous Trans-
port
HP DECnet SNA Gateway for Channel Transport
HP SNA Server for OpenVMS VAX , an OpenVMS
VAX layered product that supports local access as
well as remote DECnet clients
Features
The HP SNA Application Programming Interface for
OpenVMS (API) is a collection of subroutines designed
to provide an easy-to-use interface for the OpenVMS
application programmer who has a specic need to in-
terface to an IBM application subsystem. It supports
many different types of sessions between OpenVMS ap-
plications and applications running on an IBM host.
API implements all of the path control layer and por-
tions of the transmission and data ow control layers of
SNA. The interface supports a number of different appli-
cations, each of which uses the SNA function manage-
ment, data ow control, and transmission control layers
in a different way. API is not limited to supporting a par-
ticular application, such as 3270 terminals or Remote
Job Entry (RJE) workstations; the supported session
types are Logical Unit types 0, 1, 2, and 3, using the
FM and TS prole types 3 and 4, as described in the
product documentation.
API provides extensive parameter checking, state ma-
chine management, and other high-level services, re-
lieving the OpenVMS application programmer of tedious
protocol details such as state machine processing or
"standard" SNA message format checking. The inter-
face appears to the OpenVMS application as a set of
subroutines that it calls to request the following opera-
tions:
Establish an SNA session with an application running
on an IBM host
December 2006

Summary of content (6 pages)