EN ISP 10607-2:1996

SLOVENSKI STANDARD
01-december-1997
Information technology - International Standardized Profiles AFTnn - File Transfer,
Access and Management - Part 2: Definition of document types, constraint sets
and syntaxes (ISO/IEC ISP 10607-2:1995)
Information technology - International Standardized Profiles AFTnn - File Transfer,
Access and Management - Part 2: Definition of document types, constraint sets and
syntaxes (ISO/IEC ISP 10607-2:1995)
Informationstechnik - Internationale Profilnormen AFTnn - Dateiübermittlung, Zugriff und
Verwaltung - Teil 2: Definition von Dokumentenklassen, Zugriffseinschränkung und
Syntaxen (ISO/IEC ISP 10607-2:1995)
Technologies de l'information - Profils normalisés internationaux AFTnn - Transfert,
acces et gestion de fichier - Partie 2: Définition de types de documents, ensembles de
contraintes et syntaxes (ISO/IEC ISP 10607-2:1995)
Ta slovenski standard je istoveten z: EN ISP 10607-2:1996
ICS:
35.100.05 9HþVORMQHXSRUDEQLãNH Multilayer applications
UHãLWYH
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

INTERNATIONAL
ISO/IEC
STANDARDIZED
ISP
PROFILE
10607-2
Second edition
1995-I 2-15
Information technology - International
Standardized Profiles AFTnn - File
Transfer, Access and Management -
Part 2:
Definition of document types, constraint sets
and syntaxes
Technologies de I ’in forma tion
- Pro fils normalis& in ternationaux AFTnn -
Trans fert, acc& et gestion de fichier -
Partie 2: Dgfinition de types de documents, ensembles de contrain tes et
syntaxes
- --
Reference number
ISO/IEC ISP 10607-2:1995(E)
ISOAEC ISP 10607-2 : 1995 (E)
Contents
Page
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Foreword
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V
introduction
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.*. 1
1 Scope
1 .I General .
1.2 Position within the taxonomy .
Normative references .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.1 Identical Recommendations I International Standards
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.2 Additional references
. . . . . . . . . . . .*. 2
3 Definitions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4 Abbreviations
5 Conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
6 Document type definitions
6.1 NBS-9 File directory file document type .
6.2 INTAP-I Record file document type .
6.3 NBS-6 Sequential file document type .
6.4 NBS-7 Random access file document type . IO
6.5 NBS-8 Indexed sequential file document type . 13
6.6 NBS-10 Random binary access file document type . 16
6.7 NBS-1 1 Indexed file with unique keys document type . 18
6.8 NBS-12 Simple text file document type .
6.9 INTAP- Sequential file document type .
6.10 INTAP- Relative file document type .
6.11 INTAP- Indexed file document type .
6.12 INTAP- Indexed file with unique keys document type . 33
- -z
6.13 CGM-FTAM file document type . 37
0 ISO/lEC 1995
All ri hts resewed. Unless otherwise specified, no pat-t of this publication may be reproduced or utilized in
any 9 orm or by any means, electronic or mechanical, including photocopying and microfilm, without
permission in writing from the publisher.
ISO/IEC Copyright Office l Case postale 56 l CH-1211 GerWe 20 l Switzerland
Printed in Switzerland
0 ISOAEC
lSO/IEC ISP 10607-2 : 1995 (E)
7 Constraint sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.
7.1 NBS ordered flat constraint set .
7.2 NBS random access constraint set
..........................................................
7.3 INTAP sequential flat constraint set
.........................................................
7.4 Two levels depth hierarchical constraint set with unique names.
.................. .43
8 Abstract syntaxes .
8.1 Abstract syntax NBS-AS2
......................................................................
8.2 Abstract syntax INTAP-AS1
...................................................................
8.3 Abstract syntax NBS-AS1
......................................................................
8.4 NBS node name abstract syntax
..............................................................
8.5 NBS random binary access file abstract syntax
..........................................
8.6 NBS simple text abstract syntax
..............................................................
8.7 Abstract syntax INTAP-AS2
...................................................................
8.8 Abstract syntax INTAP-AS3
...................................................................
9 Transfer syntaxes
............................................................
9.1 Transfer syntax INTAP-TSI
....................................................................
Annexes
A Corrigenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B Main differences between the 1st edition (1990/91/94) and the
2nd edition (1995) of this part of lSO/lEC ISP 10607. . . . . . . . . . . . . . . . . 5 4
C FTAM-COBOL Language Binding for the INTAP-2, -3, -4, -5
Document Types
(Tutorial) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.l Aim of COBOL document types
...............................................................
C.2 Support range of COBOL document types
.................................................
C.3 Achievement method of COBOL document types
........................................
C.4 Mapping of COBOL data-type
.................................................................
C.5 Details of sequential file, relative file and indexed file
...................................
C.6 Mapping of FTAM service primitive and COBOL statement
........................... 65
C.7 Example of the COBOL mapping .
0 ISOAEC
lSO/IEC ISP 10607-2 : 1995 (E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide standardization.
National bodies that are members of IS0 or IEC participate in the development of International
Standards through technical committees established by the respective organization to deal with
particular fields of technical activity. IS0 and IEC technical committees collaborate in fields of
mutual interest. Other international organizations, governmental or non-governmental, in liaison
with IS0 and IEC, also take part in the work.
In the field of information technology, IS0 and IEC have established a joint technical committee,
ISO/IEC JTCI. In addition to developing International Standards, ISO/IEC JTCI has created a
Special Group on Functional Standardization for the elaboration of International Standardized
Profiles.
An International Standardized Profile is an internationally agreed, harmonized document which
identifies a standard or group of standards, together with options and parameters, necessary to
accomplish a function or set of functions.
Draft International Standardized Profiles are circulated to national bodies for voting. Publication
as an International Standardized Profile requires approval by at least 75 % of the national bodies
casting a vote.
International Standardized Profile ISO/IEC ISP 10607-2 was prepared with the collaboration of
- Asia-Oceania Workshop (AOW);
- European Workshop for Open Systems (EWOS);
- Open Systems Environment Implementors’ Workshop (OIW).
ISO/IEC ISP 10607 consists of the following parts, under the general title information technology
- International Standardized Profiles AFTnn - File Transfer, Access and Management :
- Part I: Specification of ACSE, Presentation and Session protocols for the
use by RAM
- Part 2 : Definition of document types, constraint sets and syntaxes
- Par? 3 : AFT1 I - Simple File Transfer Service (unstructured)
- Part 4 : AFT12 - Positional File Transfer Service (flat)
- Part 5 : AR22 - Positional File Access Service (flat)
- Part 6 : AFT3 - File Management Service
This second edition cancels and replaces the first edition (ISO/IEC ISP 10607-2:1990), which has
been revised. It also incorporates amendment 1: 1991 and amendment 2:1994.
Annexes A, B and C of this part of ISO/lEC ISP 10607 are for information only.

0 ISOAEC
lSO/IEC ISP 10607-2 : 1995 (E)
Introduction
This part-of ISO/IEC ISP 10607 is defined within the context of Functional Standardization,
in accordance with the principles specified by lSO/IEC TR 10000, “Framework and
Taxonomy of International Standardized Profiles ”. The context of Functional
Standardization is one part of the overall field of Information Technology (IT)
standardization activities, covering base standards, profiles, and registration
mechanisms. A profile defines a combination of base standards that collectively perform a
specific well-defined IT function. Profiles standardize the use of options and other
variations in the base standards, and provide a basis for the development of uniform,
internationally recognized system tests.
One of the most important roles for an ISP is to serve as the basis for the development (by
organizations other than IS0 and IEC) of internationally recognized tests and test centres.
ISPs are produced not simply to legitimize a particular choice of base standards and
options, but to promote real system interoperability. The development and widespread
acceptance of tests based on this and other ISPs is crucial to the successful realization of
this goal.
The text for this part of ISO/IEC ISP 10607 was developed in close co-operation among the
FTAM Expert Groups of the three International OSVOSE Workshops : OSE Implementors’
Workshop (OIW), the European Workshop for Open Systems (EWOS) and the Asia-
Oceania Workshop (AOW). This part of lSO/IEC ISP 10607 is harmonized among these
three Workshops and it was finally ratified by the Workshops’ plenary assemblies.

This page intentionally left blank

INTERNATIONAL STANDARDIZED PROFILE @ lSO/IEC
ISO/IEC ISP 10607=2:1995(E)
Information technology - International Standardized Profiles
AFTnn - File Transfer, Access and Management -
Part 2:
Definition of document types, constraint sets and syntaxes
1 Scope ITU-T Recommendation X.690 (1994) I ISO/IEC 8825
1 :I 995, Information technology - ASN. I encoding
rules : Specification of Basic Encoding Rules (BER),
1.1 General
Canonical Encoding Rules (CER) and Distinguished
This part of ISO/IEC ISP 10607 contains the basic Encoding Rules (DER).
definitions of document types, constraint sets, abstract
syntaxes, and transfer syntaxes as used and referenced
2 . 2 Additional references
in the FTAM application lSO/IEC ISP 10607-3 (AFT1 I),
IS0 1989: 1985, Programming languages - COBOL.
lSO/IEC ISP 10607-4 (AFT12), ISO/IEC ISP 10607-5
(AFT22) and lSO/IEC ISP 10607-6 (AFT3). Additional
IS0 6523: 1984, Data interchange - Structures for the
document types, constraint sets and syntaxes may be
identification of organizations.
defined and added to this part of ISO/IEC ISP 10607 to be
referenced by either the existing parts of lSO/IEC ISP
IS0 8571-I :I 988, Information processing systems -
10607 or by further parts yet to be defined.
Open Systems Interconnection - File Transfer, Access
and Management - Pa/t I : General introduction.
1.2 Position within the taxonomy
IS0 857102:1988, Information processing systems -
This part of lSO/IEC ISP 10607 is the second part, as
Open Systems Interconnection - File Transfer, Access
common text, of a multi-part ISP identified in ISO/IEC TR
and Management - Part 2 : Virtual Filestore Definition.
10000-2 as “Am, File Transfer, Access and Management”
(see also lSO/IEC TR 10000-1, 8.2 for the definition of
IS0 8571-3: 1988, Information processing systems -
multipart ISPs).
Open Systems Interconnection - File Transfer, Access
and Management - Part 3 : File Service Definition .
2 Normative references
IS0 8571-4:1988, Information processing systems -
Open Systems Interconnection - File Transfer, Access
The following documents contain provisions which,
and Management - Parf 4 : File Protocol Specification.
through reference in this text, constitute provisions of this
part of ISO/IEC ISP 10607. At the time of publication, the
IS0 8571-4: 1988/Amd.4: 1992, Information processing
editions indicated were valid. All documents are subject to
systems - Open Systems Interconnection - File
revision, and parties to agreements based on this part of
Transfer, Access and Management - Par? 4 : File
lSO/IEC ISP 10607 are warned against automatically
Protocol Specification - Amendment 4 .
applying any more recent editions of the documents listed
below, since the nature of refer,ences made by ISPs to
lSO/IEC 8571-5:1990, Information processing
such documents is that they may be specific to a systems - Open Systems Interconnection - File
particular edition. Members of IEC and IS0 maintain Transfer, Access and Management - Part 5 : Protocol
registers of currently valid International Standards and
Implementation Conformance Statement Proforma.
ISPs, and ITU-T maintains published editions of its current
ISO/I EC TR 10000-1: 1992l) , Information technology -
Recommendations.
Framework and taxonomy of International
Corrigenda to the base standards referenced : See annex
Standardized Profiles - Part I : Framework.
A for a complete list of these documents which are
ISO/I EC TR 10000-2: 1994!), Information technology -
identified in this part of ISO/IEC ISP 10607.
Framework and taxonomy of International
Standardized Profiles - Part 2 : Principles and
2.1 identical Recommendations I Inter-
Taxonomy for OSI Profiles.
national Standards
- ITU-T Recommendation X.680 (1994) I ISO/IEC 8824-
1 : 1995, Information technology - Abstract Syntax
Notation One (ASN. I): Specification of basic notation.
1 ) Currently under revision.
lSO/IEC ISP 10607-2 : 1995 (E)
0 ISOAEC
- lSO/IEC ISP 10607-1:1995, information technology -
In terna tional Standardized Profiles A FTnn - File 4 Abbreviations
Transfer, Access and Management - Part I m
This clause lists only abbreviations as used in clauses 1
Specification of ACSE, Presentation and Session
to 5.
protocols for the use by RAM.
AK Profile sub-class : File Transfer, Access and
- lSO/IEC ISP 10607-3:’ 995, Information technology -
Management
International Standardized Profiles AFTnn - File
Transfer, Access and Management - Part 3 : AFT1 I -
ASN.’ Abstract Syntax Notation One
Simple File Transfer Service (unstructured).
RAM File Transfer, Access and Management
- lSO/IEC ISP 10607-4:’ 995, Information technology -
ISP International Standardized Profile
International Standardized Profiles A FTnn - File
OSI Open Systems Interconnection
Transfer, Access and Management - Pat? 4 : AFT12 -
Positional File Transfer Service (flat).
5 Conformance
- lSO/IEC ISP 10607-5:1995, Information technology -
International Standardized Profiles A FTnn - File
No conformance requirements are specified in this part of
Transfer, Access and Management - Par? 5 : AFT22 -
lSO/IEC ISP 10607.
Positional File Access Service (fiat).
NOTE - This part of ISO/IEC ISP 10607 is a register of document
- ISO/IEC ISP 10607-6:1995, Information technology - types, constraint sets, abstract syntaxes, and transfer syntaxes.
Conformance requirements are specified in the parts of lSO/IEC
International Standardized Profiles AFTnn - File
ISP 10607 which reference these objects.
Transfer, Access and Management - Part 6 : AFT3 -
File Management Service.
3 Definitions
6 Document type definitions
The terms used in this part of ISO/IEC ISP 10607 are
The definition of “lexical order” which appears in some of
defined in the referenced base standards.
the following document type definitions, is a local
implementation issue.
- --
0 ISOAEC ISOIIEC ISP 10607-2 : 1995 (E)
6.1 NBS-9 File directory file document type
6.1.1 Entry number : NBS-9
6.3.2 Information objects
Table 1 - Information objects in NBS-9
1/ { iso identified-organization oiw( 14) ftamsig(5) document-type(5)
file-directory(g) }
“NBS-9 FTAM file-directory file”
{ iso identified-organization oiw( 14) ftamsig(5) abstract-syntax(2) nbs-as2(2) }
“NBS file directory entry abstract syntax”
transfer syntax names
{ joint-iso-ccitt asnl(1) basic-encoding( 1) }
“Basic Encoding of a single ASN.1 type”
II
parameter syntax
II
PARAMETERS : :=
[0] IMPLICIT BIT STRING {
-0
Kernel group
read-filename (0), read-permitted-actions (I),
read-contents-type (2),
-0
Storage group
read-storage-account (3), read-date-and-time-of-creation (4),
read-date-and-time-of-last-modification (5), read-date-and-time-of-last-read-access (6),
read-date-and-time-of-last-attribute-modification (7),
read-identity-of-creator (8),
read-identity-of-last-modifier (9),
read-identity-of-last-reader (IO),
read-identity-of-last-attribute-modifier (1 I),
read-file-availability (12),
read-f ilesize ( 13), read-future-filesize (14),
Security group
read-access-control (15), read-legal-qualifications (16),
Private group
read-private-use (17)
{ iso standard 8571 file-model(3) hierarchical(l) }
file model
“FTAM hierarchical file model”
constraint set { iso standard 8571 constraint-set(4) unstructured( 1) }
“FTAM unstructured constraint set”
file contents Datatypel ::= FileDirectoryEntry
-- as defined by NBS-AS2 in 8.1
II
lSO/IEC ISP 10607-2 : 1995 (E) 0 ISOAEC
Additional constraints are defined for this document type:
6.1.3 Scope and field of application
file access actions are restricted to read. File-directory
the co ntents of a file for
The document type defines
files may not be written or modified (except as a side
l=TAM.
transfer (not for storage) using
effect of actions performed on individual files contained
within a file directory).
6.1.4 References
6.1.9 Definition of transfer
IS0 8571-I :I 988, Information processing systems - Open
Sys terns Interconnection - File Transfer, Access and
6.1.9.1 Datatype definition
Management - Part I : General introduction.
The file consists of zero or more values of Datatypel
IS0 8571-2:1988, Information processing systems - Open
defined in table 1.
File Transfer, Access and
Systems interconnection -
6.1.9.2 Presentation data values
Management - Part 2 : Virtual Filestore Definition.
The document is transferred as a series of presentation
6.1.5 Definitibns
data values. Each presentation data value shall consist of
This definition makes use of the terms data element, data
one value of the ASN. 1 data type “Datatypel ”, carrying
unit and file access data unit as defined in IS0 8571-I.
one of the file directory entries from the document.
6.1.6 Abbreviations
All values are transmitted in the same (but any)
presentation context established to support the abstract
File Transfer, Access and Management
FTAM
syntax name “asnamel” declared in table 1.
National Bureau of Standards, USA
NBS
6.1.9.3 Sequence of presentation data values
6.1.7 Document semantics
The sequence of presentation data values is the same as
the sequence of file directory entries within the data unit in
The document consists of one file access data unit, which
the file.
consists only of zero, one or more data elements of type
“FileDirectoryEntry” (defined in NBS-AS2).
6.1 .I 0 Transfer syntax
The document structure takes any of the forms allowed by
An implementation supporting this document type shall
the FTAM hierarchical file model as constrained by the
support the transfer syntax generation rules named in
unstructured constraint set. These definitions appear in
table 1 for all presentation data values transferred.
IS0 8571-2.
Implementations may optionally support other named
transfer syntaxes.
The parameter of the document type is used on F-OPEN
request to specify the desired attributes of each of the
6.1.11 ASE specific specifications for FTAM
files in the filestore, when reading the document.
Relaxation is allowed to any b itstrin mbination of the
g co
6.1.8 Abstract syntactic structure
document type paramete r.
The abstract syntactic structure of the document is a
series of file directory entries, each of which is defined by
the “FileDirectoryEntry” definition in NBS-AS2.

0 ISOAEC ISO/IEC ISP 10607-2 : 1995 (E)
6.2 INTAP- Record file document type
6.2.1 Entry number : INTAP-I
6.2.2 Information objects
Table 2 - Information objects in INTAP-I
document type name { iso member-body 392 ftam( IO) document-type(2) intap-record-file( 1) }
“I NTAP record file”
abstract syntax names
name for asnamel { iso member-body 392 ftam( IO) abstract-syntax(3) intap-as1 (1) }
“INTAP abstract syntax ASI”
transfer syntax names { iso member-body 392 ftam( IO) transfer-syntax(4) intap-tsl (I) }
“INTAP transfer syntax TSI”
{ joint-iso-ccitt asnl(1) basic-encoding(l) }
“Basic Encoding of a single ASN.l type”
parameter syntax
PARAMETERS : := SEQUENCE {
maximum-record-length IMPLICIT INTEGER OPTIONAL,
[III
record-significance IMPLICIT INTEGER {variable (0), fixed (1) } OPTIONAL }
PI
{ iso standard 8571 file-model(3) hierarchical(l) }
file model
“FTAM hierarchical file model”
constraint set { iso standard 8571 constraint-set(4) unstructured( 1) }
“FTAM unstructured constraint set”
::= Record-Element -- as defined in 8.2
file contents Datatypel
6.2.3 Scope and field of application
/
unstructured
root node
/II, 1
The document type defines the contents of a file for
storage, for transfer and access by FTAM.
I
data unit
I
6.2.4 References
IS0 8571-I :I 988, Information processing systems - Open
\
Systems Interconnection - File Transfer, Access and
record record
record
\
Management - Part I : General introduction.
/I I
II I I
IS0 8571-2: 1988, Information processing systems - Open
* * * * * *
File Transfer, Access and
Systems Interconnection -
b
Management - Part 2 : Virfual Filestore Definition.
* .
. record element (data element)
6.2.5 Definitions
This definition makes use of the terms data element, data
Figure 1 - Structure of _LNTAP-1 document type
unit and file access data unit as defined in IS0 8571-I.
6.251 record : an ordered series of one or more
6.2.6 Abbreviations
record-elements. Data units of this document type consist
of one or more records (see figure I).
FADU File Access Data Unit
l=TAM File Transfer, Access and Management
INTAP Interoperability Technology Association for
Information Processing, Japan
ISOAEC ISP 10607-2 : 1995 (E) 0 ISOAEC
Boundaries between presentation data values in the
6.2.7 Document semantics
same presentation context, and boundaries between P-
The document consists of one file access data unit, which
DATA primitives, are chosen locally by the sending entity
consists only of zero, one or more records. The order of
at the time of transmission, and carry no semantics of the
each of these records is significant.
document type. Receivers which support this document
type shall accept a document with any of the permitted
The document structure takes the form allowed by the
transfer options.
FTAM hierarchical file model as constrained by the
unstructured constraint set (see table 2). These
6.2.9.3 Sequence of presentation data values
definitions appear in IS0 8571-2.
The sequence of presentation data values is the same as
Each record consists of octets of any value from 0 to 255.
the sequence of record-elements within the data unit in
The meaning attached to these values is not constrained
the file.
by the document type.
6.2.10 Transfer syntax
There are no size or length limitations imposed by this
For transferred presentation data values there are two
definition, except those specified here. Each record is of
types of transfer syntax names for INTAP-I specified in
a length determined by the number of octets given by the
table 2. They are INTAP transfer syntax TSI and Basic
maximum-record-length parameter. If this parameter is not
Encoding of a single ASN.l type. The former is used for
present, the default is that the length of records is
compression of data, and the latter is used for basic
unbounded. If the value of the record-significance
encoding (non-compression) of data. Implementations
parameter is variable, or if the parameter is not present,
supporting this document type shall support the syntax
the length of each record is less than or equal to the
for the basic encoding and may optionally support the
length given in the maximum-record-length parameter. If
syntax for compression of data. Implementations may
the value is fixed, the length of each record is exactly
optionally support other named transfer syntaxes.
equal to the length given.
6.2.11 ASE specific specifications
6.2.8 Abstract syntactic structure
6.2.11 .l String length relaxation
The abstract syntactic structure of the document is a
series of octet strings (record elements). The grouping of
String length relaxation loses explicit information in the
record elements into records is indicated by the context-
document type identification. A document of type INTAP-I
specific-number field of each record-element as specified
may be relaxed to another document of type INTAP-I with
in 8.2.
a larger maximum-record-length parameter, or no
maximum-record-length parameter.
6.2.9 Definition of transfer
6.2.11.2 The EXTEND operation
6.2.9.1 Datatype definition
of Datatypel (see When the EXTEND operation is applied to a data unit of an
The file co Insists of zero or more values
INTAP-I document, the transferred data shall be an
table 2 for the definition)
INTAP-I document with parameters equal to those of the
6.2.9.2 Presentation data values
original INTAP-I document. The resulting document
consists of the record-elements of the original INTAP-I
The document is transferred as a series of presentation
document, followed by the record-elements of the new
data values. Each presentation data value shall consist of
INTAP-I document. The boundary of the original and new
one value of ASN.l data type “Datatypel ”, carrying one of
record-elements is not visible in the new document.
the record-elements from the document. All values are
transmitted in the same (but any) presentation context
6.2.11.3 The REPLACE operation
defined to support the abstract syntax name “asnamel ”.
When the REPLACE operation is applied to the root FADU
NOTE - Specific carrier standards may impose additional
of an INTAP-I document, the transferred material shall be
constraints on the presentation context to be used, where the above
any INTAP-I document with the same parameter values.
permits a choice.
0 ISOAEC ISOAEC ISP 10607-2 : 1995 (E)
6.3 NBS-6 Sequential file document type
6.3.1 Entry number : NBS-6
6.3.2 Information objects
Table 3 - Information objects in NBS-6
{ iso identified-organization oiw( 14) ftamsig(5) document-type(5)
sequential(6) }
“NBS-6 FTAM sequential file”
abstract syntax names
a) name for asnamel { iso identified-organization oiw( 14) ftamsig(5) abstract-syntax(2) nbs-as1 (1) }
“NBS abstract syntax ASI”
b) name for asname { iso standard 8571 abstract-syntax(2) ftam-fadu(2) }
“FTAM FADU”
{ joint-iso-ccitt asn I(1 ) basic-encoding( 1) }
“Basic Encoding of a single ASN.l type”
‘.-
PARAMETERS .- SEQUENCE OF CHOICE { parameter0 ParameterO, parameter1 Parameterl,
parameter2 Parameter2 }
l ‘-
Parameter0 . .- [0] INTEGER { univer-time
J
(23)
gen-time
(24)
boolean
(1)
null
0’ 1
---
Parameter1 .- [I] SEQUENCE {
universal-class-number-l INTEGER { int
(2)
bit
(3)
ia
(22)
graphic
(25)
general
(27)
octet
L
(4) ’
string-length INTEGER }
. ‘-
Parameter2 .- [2] SEQUENCE {
private-class-number INTEGER
1 fW0) I,
length-l INTEGER,
length-2 INTEGER }
file model { iso standard 8571 file-model(3) hierarchical(l) }
“FTAM hierarchical file model”
{ iso standard 8571 constraint-set(4) sequential-flat(2) }
constraint set
- -l
“FTAM sequential flat constraint set”
file contents Datatypel ::= PrimType --as defined by NBS abstract syntax AS1 in 8.3
Datatype ::= Node-Descriptor-Data-Element

ISOAEC ISP 10607-2 : 1995 (E) 0 ISOAEC
6.3.3 Scope and field of application 6.3.9 Definition of transfer
The document type d efines the contents of a file for 6.3.9.1 Datatype definitions
storage, for transfer and access by FTAM.
The file consists of data values which are of either
NOTE - Storage to apparent storage within the virtual
filestore.
a) Datatypel defined in table 3, where the PrimType in the
datatype is given by the NBS-AS1 definition; or
6.3.4 References
b) Datatype defined in table 3, the ASN.l datatype
IS0 8571-I :I 988, Information processing systems - Open
declared as “Data-Element” in the ASN.l module
File Transfer, Access and
Sys terns Interconnection -
IS08571 -FADU.
Management - Part I : General introduction.
6.3.9.2 Presentation data values
IS0 8571.2:1988, Information processing systems - Open
Systems Interconnection - File Transfer, Access and
The document is transferred as a eries of
presentation
Management - P>rt 2 : Virtual Filestore Definition.
data values, each of which is either
6.3.5 Definitions
a) one value of the ASN.l datatype “Datatypel ”, carrying
one of the data elements from the document. All values
This definition makes use of the terms data element, data
are transmitted in the same (but any) presentation context
unit and file access data unit as defined in IS0 8571-1.
established to support the abstract syntax name
“asnamel “; or
6.3.6 Abbreviations
b) a value of “Datatype2 ”. All values are transmitted in the
FTAM File Transfer, Access and Management
same (but any) presentation context established to
support the abstract syntax name “asname2 ”.
6.3.7 Document semantics
NOTES
The document consists of zero, one or more file access
data units. Each FADU contains precisely zero or one
1 Specific carrier standards may impose additional constraints on
the presentation context to be used, where the above permits a
data unit which consists of zero, one or more data
choice.
elements. The order of each of these elements is
significant.
2 Any document type defined in this
entry either makes no use of
Datatype2, or starts with a Datatype
transmission.
The document structure takes any of the forms allowed by
the FTAM hierarchical file model as constrained by the
Boundaries between presentation data values in the same
sequential flat constraint set (see table 3). These
presentation context, and boundaries between P-DATA
definitions appear in IS0 8571-2. As additional
primitives, are chosen locally by the sending entity at the
constraints FADU Identity will be limited to begin, end, first
time of transmission, and carry no semantics of the
and next.
document type. Receivers which support this document
type shall accept a document with any of the permitted
For a specific file the number of data elements in a data
transfer options (e.g., document type parameters and
unit is given by the parameters. Each data element is a
transfer syntaxes).
data type from the set of primitive data types defined in
8.3. Each data unit contains the same data element types
6.3.9.3 Sequence of presentation data values
in the same order as all other data units. These types are
determined by the parameters 0 through 2. The sequence of presentation data values of type a) and
the sequence of presentation data values of types a) and
For Datatypel, the string-length field of Parameter1
b) is the same as the sequence of data elements within a
specifies the length of the value in octets for the
data unit, and data units in the hierarchical structure,
INTEGER, BIT STRING and OCTET STRING types. For
when flattened according to the definition of the
character-type data elements, the string-length indicates
hierarchical file model in IS0 8571-2.
the actual number of characters from the specified
character set, not including any escape sequences or 6.3.10 Transfer syntax
overhead from the character encoding.
An implementation supporting this document type shall
For floating point numbers, finite form, length-l and support the transfer syntax generation rules named in
table 3 for all presentation data values transferred.
length-2 specify the length in bits of mantissa and
exponent, respectively. The length-l and length-2 values
Implementations may optionally support other named
are irrelevant for the other choices of floating point
transfer syntaxes.
numbers.
- -z
6.3.11 ASE specific specifications
6.3.8 Abstract syntactic structure
6.3.11 .I Structural simplification
The abstract syntactic structure of the document is a
hierarchically structured file as defined in the ASN.l
This simplification loses information.
module IS08571-FADU in IS0 8571-2, in which each of
the file access data-units has the abstract syntactic
The document type NBS-6 may be simplified to the
structure of NBS-AS1 as defined by the parameters.
document type FTAM-3 (allowed only when reading the
file). The octet representation of the transferred data is

0 ISOAEC
ISOAEC ISP 10607-2 : 1995 (E)
unpredictable. It will usually correspond to the data values
6.3.11.3 The INSERT operation
as stored in the local real filestore of the responder.
When the INSERT operation is applied at the end of file,
6.3.11.2 Access context selection
the transferred material shall be the series of FADUs
which would be generated by reading any NBS-6
A document of type NBS-6 may be accessed in any one of
document with the same parameter values in access
the access contexts defined in the sequential flat
context FA.
constraint set. The presentation data units transferred in
each case are those derived from the structuring
elements defined for that access context in IS0 8571-2.

lSO/IEC ISP 10607-2 : 1995 (E) 0 ISOAEC
6.4 NBS-7 Random access file document type
6.4.1 Entry number : NBS-7
6.4.2 Information objects
Table 4
- Information objects in NBS-7
document type name { iso identified-organization oiw( 14) ftamsig(5) document-type(5)
random-file(7) }
“NBS-7 FOAM random acess file”
abstract syntax names
a) name for asnamel { iso identified-organization oiw( 14) ftamsig(5) abstract-syntax(2) nbs-as1 (1) }
“NBS abstract syntax ASI”
{ iso standard 8571 abstract-syntax(2) ftam-fadu(2) }
b) name for asname
“FTAM FADU”
I
transfer syntax names { joint-iso-ccitt asn I(1 ) basic-encoding( 1) }
“Basic Encoding of a single ASN.l type”
parameter syntax
-*-
SEQUENCE OF CHOICE { parameter0 ParameterO, parameter1 Parameterl,
PARAMETERS .-
parameter2 Parameter2 }
-*-
..- univer-time
Parameter0 [0] INTEGER ( 9
(23)
gen-time
(24)
boolean
(1)
null
(5)’ I
l --
Parameter1 .- [I] SEQUENCE {
universal-class-number-l INTEGER
{ int
(2) 9
bit
(3) 9
ia
(22)
graphic
I
(25)
general
(27)
octet
(4) i
string-length INTEGER }
-9-
Parameter2 .- [2] SEQUENCE {
private-class-number INTEGER
{ float (0) 1,
length-l INTEGER,
length-2 INTEGER }
file model { iso standard 8571 file-model(3) hierarchical(l) )
“FAM hierarchical file model”
constraint set { iso identified-organization oiw( 14) ftamsig(5) constraint-set(4)
nbs-ordered-flat( I) }
- --
“NBS ordered flat constraint set”
file contents Datatypel ::= PrimType --as defined by NBS abstract syntax AS1 in 8.3
Datatype ::= CHOICE { node-descriptor-data-element Node-Descriptor-Data-Element,
enter-subtree-data-element Enter-Subtree-Data-Element,
exit-subtree-data-element Exit-Subtree-Data-Element }
0 ISO/IEC ISOAEC ISP 10607-2 : 1995 (E)
6.4.3 Scope and field of application 6.4.9 Definition of transfer
The document type defines the contents of a file for 6.4.9.1 Datatype definitions
storage, for transfer and access by FTAM.
The file consists of data values which are of either
NOTE - Storage refers to apparent storage within the virtual
filestore.
a) Datatypel defined in table 4, where the PrimType in the
datatype is given by the NBS-AS1 definition; or
6.4.4 References
b) Datatype defined in table 4, the ASN.l datatype
IS0 8571-I : 1988, Information processing systems - Open
declared as “Data-Element” in the ASN.l module
Systems interconnection - File Transfer, Access and
IS08571 -FADU.
Management - Part I : Genera/ introduction.
6.4.9.2 Presentation data values
IS0 8571.2:1988, Information processing systems - Open
Systems Interconnection - File Transfer, Access and
The document is transferred as a series of presentation
Management - Part 2 : VirWal Filestore Definition.
data values, each of which is either
6.4.5 Definitions
a) one value of the ASN.l datatype “Datatypel ”, carrying
one of the data elements from the document. All values
This definition makes use of the terms data element, data
are transmitted in the same (but any) presentation context
unit and file access data unit as defined in IS0 8571-1.
established to support the abstract syntax name
“asnamel “; or
6.4.6 Abbreviations
b) a value of “Datatype2 ”. All values are transmitted in the
FTAM File Transfer, Access and Management
same (but any) presentation context established to
support the abstract syntax name “asname2 ”.
6.4.7 Document semantics
NOTES
The document consists of zero, one or more file access
data units. Each FADU contains precisely zero or one
1 Specific carrier standards may impose additional constraints on
data unit which consists of zero, one or more data the presentation context to be used, where the above permits a
choice.
elements. The order of each of these elements is
significant.
2 Any document type defined in this entry either makes no use of
Datatype2, or starts with a Datatype transmission.
The document structure takes any of the forms allowed by
the FTAM hierarchical file model as constrained by the
Boundaries between presentation data values in the
NBS-ordered-flat constraint set (see table 4). These
same presentation context, and boundaries between P-
definitions appear in 7.1.
DATA primitives, are chosen locally by the sending entity
at the time of transmission, and carry no semantics of the
For a specific file the number of data elements in a data
document type. Receivers which support this document
unit is given by the parameters. Each data element is a
type shall accept a document with any of the permitted
data type from the set of primitive data types defined in
transfer options (e.g., document type parameters and
8.3. Each data unit contains the same data element
transfer syntaxes).
types in the same order as all other data units. These
types are determined by the parameters 0 through 2.
6.4.9.3 Sequence of presentation data values
For Datatypel , the string-length field of Parameter1
The sequence of presentation data values of type a) and
specifies the length of the value in octets for the
the sequence of presentation data values of types a) and
INTEGER, BIT STRING and OCTET STRING types. For
b) is the same as the sequence of data elements within a
character-type data elements, the string-length indicates
data unit, and data units in the hierarchical structure,
the actual number of characters from the specified
when flattened according to the definition of the
character set, not including any escape sequences or
hierarchical file model in IS0 8571-2.
overhead from the character encoding.
6.4.10 Transfer syntax
For floating point numbers, finite form, length-l and
length-2 specify the length in bits of mantissa and An implementation supporting this document type shall
exponent, respectively. The length-l and length-2 values support the transfer syntax generation rules named in
are irrelevant for the other choices of floating point table 4 for all presentation data values transferred.
numbers.
amed
Implementation may optionally support other n
Abstract syntactic structure transfer syntaxes.
6.4.8
- --
6.4.1 1 ASE specific specifications
The abstract syntactic structure of the document is a
hierarchically structured file as defined in the ASN.l
6.4.11 .I Structural simplification
module IS08571-FADU in IS0 8571-2, in which each of
the file access data units has the abstract syntactic
This simplification loses information.
structure of NBS-AS1 as defined by the parameters.
The document type NBS-7 may be accessed as a
document type FTAM-3 (allowed only when reading the
file) by specifying document type R-AM-3 in the contents
ISOAEC ISP 10607-2 : 1995 (E)
0 ISOAEC
type parameter in F-OPEN request, and limiting access 6.4.11.2 Access context selection
context to UA on F-READ.
A document of type NBS-7 may be accessed in any one of
the access contexts defined in the NBS ordered flat
The octet representation of the transferred data is
unpredictable. It will usually correspond to the data values
...