OSI/FTAM Programming Guide

HP NonStop OSI/FTAM Programming Guide—528612-001
3-1
3 NonStop FTAM Programming
This section presents programming concepts and tasks important to application
development in the NonStop FTAM environment using the NonStop initiator. This
section covers these topics:
Association Establishment Concepts
A connection between an FTAM initiator and a remote FTAM responder is an
association. To develop and manage an application using the NonStop FTAM initiator,
you must understand these concepts related to association establishment:
•
Connection endpoint identifier
•
APLMGR process name
•
OSI addresses and common names
•
Subdevices
•
Steps to establishing an association
•
Wait and nowait modes
Connection Endpoint Identifier (CEPI)
Associations between initiators and responders make FTAM communication across a
network possible. To perform an operation between the local NonStop initiator and
remote responder using NonStop FTAM procedures, you must first establish an
association between these entities. FTAM associations are established using the OSI
protocol services on the local and remote computer systems.
NonStop FTAM applications use the connection endpoint identifier (CEPI) to identify
the associations that the NonStop initiator establishes with remote responders across
the network. Each FTAM association that your NonStop FTAM application initiates
using the FTM_INITIALIZE_REQ_ procedure is automatically assigned a unique CEPI
by the FTAM application programmatic interface (API). The CEPI is typically the first
parameter in NonStop FTAM procedure calls and is a required parameter. After an
association is established, you must use the CEPI every time you call a procedure to
act on that association. A valid CEPI is an integer between -10 and -32767. A returned
CEPI value of -1 indicates an error condition.
Topic Page
Association Establishment Concepts
3-1
Data Transfer Concepts 3-11
FTAM API Concepts 3-31
Error-Handling Concepts 3-39