OSI/FTAM Programming Reference Manual

Running H/F 1
HP NonStop OSI/FTAM Programming Reference Manual—528611-001
3-6
Running H/F 2
Response Procedures
Response procedures have names in the form FTM_xxx_RSP_, where xxx refers to
the specific FTAM primitive. While the responder is the sender of most responses to
the initiator (in response to initiator requests), the initiator can also send a cancel
response after receiving a cancel indication from the responder.
For further information on using the cancel response procedure, refer to the
information about the FTM_CANCEL_RSP_ procedure call in the OSI/FTAM
Programming Guide and in Section 4, FTM Procedures.
Confirm Procedures
Confirm procedures have names in the form FTM_xxx_CNF_, where xxx refers to the
specific FTAM primitive. The initiator receives confirm primitives as a result of
responses sent by the responder. Confirm procedures allow your application to extract
from the confirm primitive the results of the responder’s attempts to perform requested
services.
For further information on using confirm procedures, refer to the appropriate procedure
call information in the OSI/FTAM Programming Guide and in Section 4, FTM
Procedures.
Grouped Procedures
Most of the FTM procedures are associated with a single FTAM primitive. For example,
the FTM_INITIALIZE_REQ_ procedure issues only the F-INITIALIZE primitive.
However, two FTM procedures, called grouped procedures, issue several primitives:
FTM_FILE_OPEN_REQ_ and FTM_FILE_CLOSE_REQ_.
The grouped procedure FTM_FILE_OPEN_REQ_, for example, issues the primitives
F-SELECT or F-CREATE, and F-OPEN, which allows you to select or create a file and
then open it in a single procedure call. The grouped procedure
FTM_FILE_CLOSE_REQ_ issues the primitives F-CLOSE and either F-DESELECT or
F-DELETE, allowing you to close and either deselect or delete a file in a single
procedure call. The request primitives for both the file-open and file-close services are
bracketed with the F-BEGIN-GROUP and F-END-GROUP primitives.
Two confirm procedures, FTM_FILE_OPEN_CNF_ and FTM_FILE_CLOSE_CNF_,
complete the request-confirm pairings of the file-open and file-close operations, as
shown in the table in the following subsection.
Mapping of Primitives to Procedures
Table 3-1 on page 3-7 lists the ISO FTAM service primitives and the corresponding
NonStop FTAM procedures. The F-BEGIN-GROUP and F-END-GROUP confirms do
not use an FTM_xxx_CNF_ procedure call. Because no parameters are passed in the
two primitives, a confirm procedure to retrieve data is unnecessary.