OSI/FTAM Programming Reference Manual

Running H/F 1
HP NonStop OSI/FTAM Programming Reference Manual—528611-001
3-5
Running H/F 2
How FTM Procedures Are Categorized
FTM procedures are categorized according to the four types of FTAM primitives:
request, indication, response, and confirm. FTM procedures typically send primitives
that operate in request-indication and response-confirm pairs. The initiator typically
generates requests locally, and a remote FTAM responder receives them as
indications. The responder typically generates responses that the initiator receives as
confirms.
For example, to establish an association, you call the FTM_INITIALIZE_REQ_
procedure and generate a request primitive. The initiator sends the request primitive
across the network as an encoded message, or FTAM protocol data unit (FPDU), to
the remote responder, which receives the request as a corresponding indication. The
responder establishes an association with the initiator and sends back a response to
the initiator. The initiator receives the response as a corresponding confirm. The
following subsections describe these four categories of FTM procedures and their
relationships during an association. A fifth subsection describes the FTAM API grouped
procedures, which allow an application to perform several file operations as a grouped
service.
Request Procedures
Request procedures have names in the form FTM_xxx_REQ_, where xxx refers to
the specific FTAM primitive. When you call a request procedure, the initiator validates
the request and, when it detects an error, it returns an error message to your
application. If the initiator finds no protocol error, the initiator encodes the
corresponding FPDU to send across the network. The initiator then forwards the FPDU
to the remote responder to ask for the specified service. The responder receives the
FPDU as the corresponding indication. For a more detailed description of FPDUs, see
the OSI/FTAM Programming Guide.
For further information on using request procedures, refer to the appropriate procedure
call information in the OSI/FTAM Programming Guide and in Section 4, FTM
Procedures.
Indication Procedures
Indication procedures have names in the form FTM_xxx_IND_, where xxx refers to
the specific FTAM primitive. While the responder is the recipient of most indications (as
a result of initiator requests), the initiator can also receive indications. The abort,
cancel, and data-transfer services allow the initiator to receive indications from the
remote responder.
For further information on using indication procedures, refer to the appropriate
procedure call information in the OSI/FTAM Programming Guide and in Section 4, FTM
Procedures.