OSI/FTAM Programming Guide

NonStop FTAM Programming
HP NonStop OSI/FTAM Programming Guide—528612-001
3-22
FTAM-2 Files
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, where the maximum value is 7148 bytes. 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-1
Documents
The Guardian file type corresponding to an FTAM-1 file is a standard EDIT file. Like
other unstructured files on the NonStop system, it is simply a long string of bytes, as
shown in Figure 3-7. If you want to create such a file for use with NonStop FTAM, use
these parameters:
•
File type must be Unstructured (0).
•
File code can be anything you want, avoiding codes 100 through 999, but if you
want to operate on the file later as an EDIT file, or if you want to make it accessible
to other users through the NonStop FTAM responder, use file code 101.
•
Extent sizes and number of extents, which determine the size of the file, should be
consistent with the requirements of your application, for instance, large enough to
hold the data you expect to transfer into the file.
To find out how to perform local operations on unstructured files, see the ENSCRIBE
Programmer’s Guide.
FTAM-2 Files
An FTAM-2 file is a sequential text file. For details about FTAM-2 files, refer to
Section 2, ISO FTAM Concepts or ISO 8571, Part 2.
Writing FTAM-2 Files
To write an FTAM-2 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 insert. You must use a fadu-id (ZFTM-DDL-FADU-ID) parameter
value of end and a fadu-operation parameter value of insert on the
Figure 3-7. Unstructured Files on the NonStop System
VST0307.vsd
0
512 1024 1536 3584
4096
(EOF)
Relative Byte Address