OSI/FTAM Programming Guide

ISO FTAM Concepts

HP NonStop OSI/FTAM Programming Guide—528612-001

2-29

Object Identifiers

The list of numbers in braces ({}) under the document type names and constraint sets

in Table 2-8 on page 2-28 are object identifier values. The object identifier uniquely

identifies several types of different information including, but not limited to, document

type names and constraint sets. Specific values for object identifiers are assigned by

ISO and other organizations. In writing FTAM applications, you will often have to use

object identifiers to represent document types.

Object identifiers consist of a series of two or more values enclosed in braces. In this

manual, the values are represented either by numbers, or by names and numbers.

Some examples follow:

{ iso(1) identified-organization(3) oiw(14) ftamsig(5) document-type(5) file

directory(9) }

{1 0 8571 5 1}

{ iso(1) standard(0) 8571 document-type(5) unstructured-text(1) }

The first example represents the object identifier for the NBS-9 document type, and the

second two examples represent different forms of the object identifier for the FTAM-1

document type.

For additional details about encoding object identifiers, refer to ISO 8824, Section 26.

For more information on FTAM object identifiers, refer to ISO 8571-1, Annex B.

FTAM-1 Documents

The FTAM-1 document is an unstructured text file. It consists of a root node with a data

unit (which can be empty), but no node name. The data unit is composed of zero, one,

or more character strings and has no size or length limitations.

Because there is only one data unit, access to part of an FTAM-1 file is not allowed.

The responder can perform these actions on an FTAM-1 file: read, replace, extend,

and erase. The locate action is not possible. The only FADU identity used is first, which

identifies the FADU corresponding to the root node. You therefore perform file-access

actions on the FTAM-1 file as a whole.

FTAM-1 files can use only one access-context value: unstructured all-data units (UA).

In the UA access context, only file-contents data elements are transferred. (The

concept of structuring data elements does not apply to an unstructured file.) This

means that only the data contents of FTAM-1 files are transferred.

An FTAM-1 file is equivalent to an EDIT file (file code 101) on the NonStop system.

FTAM-2 Documents

An FTAM-2 document is a sequential text file. Figure 2-8 on page 2-30 shows its

structure. FTAM-2 documents consist of a root node without an associated data unit

and zero, one, or more child nodes, each with an associated data unit. In addition, a