OSI/FTAM Programming Reference Manual

FTM Procedures
HP NonStop OSI/FTAM Programming Reference Manual—528611-001
4-7
FTAM Protocol Dependencies
Every FTAM procedure uses cepi, and all request procedures made in nowait mode
can optionally use tag. Most indication and confirm procedures can but do not have to
use the diagnostic and action-result parameters.
FTAM Protocol Dependencies
FTAM protocol requires that you call most FTM procedures only when the association
is within a particular FTAM regime. Table 4-2 summarizes these regime requirements
for calling the FTM procedures. The table does not reflect regime transitions caused by
the issuing of individual calls or the grouping of confirmed services. For example,
grouped procedures, such as FTM_FILE_OPEN_REQ_ and
FTM_FILE_CLOSE_REQ_, allow an association to move through several regimes at
the same time.
service-
class
FTM_INITIALIZE_CNF_ Output ZFTM-DDL-SERVICE-
CLASS
Optional
FTM_INITIALIZE_REQ_ Input Optional
start-
position
FTM_DATA_IND_ Input INT(32) Optional
state-
result
FTM_CREATE_CNF_ Output INT(32) Optional
FTM_FILE_OPEN_CNF_ Output Optional
FTM_INITIALIZE_CNF_ Output Optional
FTM_OPEN_CNF_ Output Optional
FTM_SELECT_CNF_ Output Optional
tag All request and response
procedures
Input INT(32) Optional
threshold FTM_BEGIN_GROUP_REQ_ Input INT(32) Required
wait-mode FTM_INITIALIZE_REQ_ Input INT Optional
Table 4-2. FTM Procedure Regime Dependencies (page 1 of 3)
Regime Requirement Procedure
Prior to Association Establishment FTM_INITIALIZE_CNF_
FTM_INITIALIZE_REQ_
Must be in FTAM regime FTM_CREATE_CNF_
FTM_CREATE_REQ_
FTM_FILE_OPEN_CNF_
FTM_FILE_OPEN_REQ_
Table 4-1. FTM Procedure Parameters and Associated Calls (page 5 of 5)
Parameter Procedure Calls
Input
or
Output Data Type Parameter