FTAM/9000 Programmer's Guide

48 Chapter 2
Using HP FTAM/9000
Using Regimes
• After exiting an inner regime, you can re-enter the same regime (e.g.,
you can sequentially select several files in the FTAM regime).
• You can terminate all regimes, no matter how deeply nested, using
the abort request (ft_abort()).
Using the FTAM Regime
The FTAM functions requested during this regime are negotiated
between the initiator and responder during the protocol exchange. (The
initiator supplies information which the responder then verifies.)
Your FTAM application must supply the initiator identity. You may also
request (i.e., try to negotiate) certain document types (file types),
attribute groups, service classes, and functional units. Refer to the
“FTAM Data Structures” chapter for detailed information regarding
these negotiated services.
The responder verifies requests in one of the following ways.
• Returns a positive confirmation that it accepts the request with no
changes.
Document
Types
File types FTAM-1, FTAM-2, FTAM-3, INTAP-1,
and NBS-9. FTAM-1 is a text file, FTAM-2 is a
record-oriented text file, FTAM-3 is a binary file,
INTAP-1 is a record- oriented binary file, and
NBS-9 is a directory.
Attribute
Groups
Organize specific qualities or characteristics to a
file (e.g., name and size); identify subsets of
attributes.
Service
Classes
Organize functional units into meaningful groups.
Each service class identifies mandatory and
optional functional units.
Functional
Units
Specify which FTAM functions, within the selected
service class, are allowed. The mandatory and
optional functional units depend on the service
class, which must support all selected functional
unit values.