OSI/FTAM Programming Reference Manual

HP NonStop OSI/FTAM Programming Reference Manual—528611-001
3-1
3 NonStop FTAM Initiator
The NonStop FTAM initiator allows applications running on a NonStop system to
access FTAM protocol and to request services of a responder across the OSI network.
It is responsible for initiating and managing the associations between NonStop FTAM
applications and remote FTAM applications. The initiator communicates with
application programs through the FTAM application programmatic interface (API). The
OSI/AS API provides the initiator interface with the OSI/AS subsystem.
This section covers the following topics:
This information is intended for programmers writing applications for NonStop systems
that will interact with FTAM responders on remote systems.
Initiator Structure
The initiator can be broken down into two main components that provide FTAM
functions to the FTAM application. These components process FTAM requests,
perform the requested operations, and communicate with the requesting application
processes.
Figure 3-1 on page 3-2 focuses on the initiator components essential to programming
and does not reflect the parts of the initiator that format data or process management
messages, for example. For diagrams reflecting the global system architecture of
NonStop FTAM, see Section 1, Introduction to NonStop OSI/FTAM.
Figure 3-1 on page 3-2 shows the following initiator components:
•
The protocol state machine receives FTAM requests from the FTAM API. It checks
the validity of the FTAM requests, translates them into the appropriate FTAM
primitives (generally requests or responses), and sends them through the OSI/AS
API to the TAPS process of the OSI/AS subsystem.
The protocol state machine also checks the validity of confirms and indications as
they come in from the TAPS process.
•
The OSI/AS API is the programmatic interface between the initiator and the
OSI/AS subsystem. The initiator communicates with underlying NonStop OSI/AS
processes through this interface.
Topic Page
Initiator Structure
3-1
Initiator Data Flow 3-3
Types of Procedures in the FTAM API 3-4
How FTM Procedures Are Categorized 3-5
Supported Functions 3-9
Accessing Local Information 3-11