OSI/FTAM Programming Guide

NonStop FTAM Programming
HP NonStop OSI/FTAM Programming Guide—528612-001
3-28
FTAM-3 Files
string-significance parameter value of ZFTM-VAL-STRINGSIG-VARIABLE, see
Figure 3-6 on page 3-21.
Reading FTAM-3 Files
To read an FTAM-3 file, you must first open the file (using FTM_OPEN_REQ_ or
FTM_FILE_OPEN_REQ_) with a process-mode (ZFTM-DDL-PROC-MODE)
parameter value of read. A fadu-id (ZFTM-DDL-FADU-ID) parameter value of first
must be used on the FTM_READ_REQ_ call. The entire file is then returned by
successive F-DATA indication events. After receiving each data indication event
(ZFTM-VAL-EVT-DATA-IND), call FTM_DATA_IND_ one or more times to retrieve the
data. Each encoded octet string in the F-DATA indication is placed in a separate data
element as raw data.
The initiator checks the length of each string against the maximum-string-length
value proposed in the contents-type parameter of the open request or returned in
the open confirm. If the string length is greater than the proposed maximum-string-
length, the initiator issues a provider abort.
Files on the NonStop System Compatible with FTAM-3
Documents
The Guardian file type corresponding to an FTAM-3 file is either an unstructured file or
an entry-sequenced file. Specifically, if the string-significance is fixed or variable, the
corresponding file type is entry-sequenced; if the string-significance is not significant,
the corresponding file type is unstructured. An unstructured file is simply a string of
bytes, as shown in Figure 3-7 on page 3-22; the structure of an entry-sequenced file is
shown in Figure 3-11 on page 3-29, with each record of the file corresponding to a
string as defined by FTAM.