Introduction to Networking for NonStop S-Series Servers

Open Systems Interconnection (OSI) Network
Connections
Introduction to Networking for HP NonStop S-Series Servers—520670-005
8-8
File Transfer, Access, and Management (OSI/FTAM)
product is running. In fact, the OSI configuration is preserved through the failure; the
application need only reestablish the connection with the remote system.
In addition to the HP fundamentals, your applications have access to other software on
the NonStop S-series server, for example, HP NonStop SQL/MP. (See Figure 8-5 on
page 8-17.)
File Transfer, Access, and Management
(OSI/FTAM)
HP NonStop OSI/FTAM is an implementation of the ISO FTAM standard. It is also
consistent with the Government Open Systems Interconnection Profile (GOSIP), which
specifies standards an OSI implementation must meet to be used for government
applications. (HP FTAM complies with U.S. GOSIP versions 1 and 2 and United
Kingdom GOSIP version 3.0, supporting the A1, M1, and T2 profiles of versions 1 and
2 and the A122, A3, and A112 profiles of version 3.0.)
With HP FTAM your applications can exchange and manage files across an OSI
network, with record-level access to structured text files, including row access to SQL
tables. You can copy, move, and delete the following kinds of files, and discover and
modify a range of file attributes:
•
Unstructured text files (called FTAM-1 files)
•
Structured text files (called FTAM-2 files)
•
Binary files (called FTAM-3 files)
Your applications can find and read specific records and insert records at the end of
FTAM-2 files. They can also read directory files (called NBS-9 files).
HP FTAM includes initiator and responder processes. The initiator process accepts
requests from applications on the NonStop S-series server and sends the requests to
remote systems where the target files are located. The responder receives requests
from FTAM processes on other systems in the network and performs the operations on
files stored on the NonStop S-series server. The set of functions you can perform on
remote files is the same as the set of functions remote applications can perform on HP
files (unless the other system is more restrictive in the functions it supports).
The API to the initiator process consists of procedures that correspond directly to
FTAM primitives and allows your application direct control of the FTAM protocol. The
interface supports all standard FTAM primitives except F-Recover, F-Check, and
F-Restart.
The FTAM standard groups primitives in two major ways. Functional units are
collections of primitives supporting specific types of operations. HP FTAM supports the
following functional units: kernel (which includes the basic services for establishing and
releasing FTAM associations), read, write, file access, limited and enhanced file
management, and grouping (which lets several primitives be combined in a single
request message to the remote system). Service classes specify the range of
functions available to applications during their association. HP FTAM supports the