ISO 8571-3:1988/Amd 1

Title missing - Legacy paper document

General Information

• Status: Withdrawn
• Publication Date: 31-Dec-1987
• Technical Committee: ISO/TMBG - Technical Management Board - groups
• Drafting Committee: ISO/TMBG - Technical Management Board - groups
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 01-Jan-1993

Standards Content (Sample)

I NTE R NAT1 ON AL IS0
857 1-3
STANDARD
First edition
1988-10-01
AMENDMENT 1
1992-12-15
information processing systems - Open Systems
Interconnection - File Transfer, Access and
Management -
Part 3 :
File Service Definition
AMENDMENT 1 : Filestore Management
Technologies de l’information - Interconnexion de systèmes ouverts (OW -
Transfert, accès et gestion de fichiers -
Partie 3: Définition du service de fichiers
AMENDEMENT I : Gestion du système de fichiers
Reference number
IS0 8571-3:1988/Amd.l :I992 (E)
..
.....

---------------------- Page: 1 ----------------------
- IS0 8571-3:1988/Amd.l:1992 (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 and 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 JTC 1. Draft International Standards adopted by the
joint technical committee are circulated to national bodies for voting. Publication
as an International Standard requires approval by at least 75 % of the national
bodies casting a vote.
Amendment 1 to International Standard IS0 8571-3:1988 was prepared by Joint
Technical Committee ISO/IEC JTC 1, Information technology.
IS0 8571-3 consists of the following parts, under the general title Information
processing systems - Open Systems Interconnection - File Transfer, Access and
Management
- Part I : General introduction
- Part 2 : Virtual Filestore Definition
- Part 3 : File Service Definition
- Part 4 : File Protocol Specification
- Part 5 : Protocol Implementation Conformance Statement Proforma
O ISO/IEC 1992
All rights reserved. No part of this publication may be reproduced or utilized in any form or by
any means, electronic or mechanical, including photocopying and microfilm, without
permission in writing from the publisher.
Case postale 56 CH-1211 Genève 20 Switzerland
ISOAEC Copyright Office
Printed in Switzerland
ii

---------------------- Page: 2 ----------------------
IS0 857 1-3:1988/Amd.l A992 (E)
Information processing systems - Open Systems
Interconnection - File Transfer, Access and Management -
Part 3 :
File Service Definition
j AMENDMENT 1 : Filestore Management
I
NOTE -This amendment has additional subclauses and tables to IS0 8571:1988 which are indicated by the use of lower
case Roman letters beginning with "a" and imply ordering alphabetically, following the clause with the same numerical
value in IS0 8571. These and all subsequent subclauses, tables, and cross references will be renumbered in subsequent
editions.
O Introduction (amend 4th paragraph, page 1)
IS0 8571 defines a basic file service. It provides
(amend 3rd paragraph, page 1)
sufficient facilities to support file transfer, file access
IS0 8571 defines services for file transfer, access and
and management of files stored on open
management. It also specifies a protocol available
857, does not specifL the interfaces to a fi,e
within the application layer Of the Reference Model*
transfer, access or management facility within the l0-l
The service defined is of the category Application
system.
Service Element (ASE). It is concerned with
identifiable bodies of information which can be treated
as files, stored and managed within open systems, or
passed between application processes.

---------------------- Page: 3 ----------------------
IS0 857 1-3: 1988/Amd. 1: 1992 (E)
Section one: General
6.2 File service levels
Eight services are associated with filestore
management:
(amend 1st paragraph's item (a), page 3)
the change current name prefix seirvice (see
a) the external file service (EFS), in which the user
clause 14a.l) is used by the initiator to control
states its FTAM quality of service requirements,
the mapping of incomplete pathnames to
but has no awareness of error recovery,
complete pathnames during the current
delegating such considerations to the service
association;
provider. Transfer of file data and other
operations on the filestore are modeled in the
the list file-directory service (see clause 14a.2) is
external file service as a series of error-free
used by the initiator to interrogate for the
operations. Thus within the external file service
attributes of objects which correspond to a given
there is no visibility of recoverable errors or the
attribute value assertion list in or under a file-
error recovery actions;
directory;
6.3 Regimes of the file service
the generalized selection service (see clause
14b.l) is used by the initiator to identify a group
(amend 1st paragraph, page 4)
of pathnames of files with attributes
Four types of file service regime are defined:
corresponding io a given attribute value
assertion list;
a) the RAM regime, existing while the application
association is used for the FTAM protoco1,with the group deletion service (see ciausit 14b.2) is
which a group of file object complete pathnames
used by the initiator to remove the file objects
is associated;
identified by pathnames in the generalized se-
lection group such that the objects cease to
b) the object selection regime during which a
exist.
particular object is associated with the FTAM
regime;
the group move service (see clause 14b.3) is
used by the initiator to transfer the fiile objects
c) the file open regime during which a particular set
identified by pathnames in the generalized se-
of processing mode, presentation contexts and
lection group to a destination directory
concurrency controls is in operation;
the group copy service (see clause 14b.4) is
d) the data transfer regime during which a
used by the initiator to duplicate the file objects
particular bulk data transfer specification and
identified by pathnames in the generalized se-
direction of transfer are in force.
lection group to a destination directory.
(amend 3rd paragraph, page 4)
the group list service (see clause 14b.5) is used
The file service provides for: by the initiator to interrogate the pattinames of
the file objects in the generalized selection
e) a sequence of object selection regimes in an
group.
FTAM regime;
the group change attribute service (see clause
f) a sequence of file open regimes in an object
14b.6) is used by the initiator to modify the at-
selection regime;
tributes of file objects, identified by complete
pathnames within the generalized selection
g) a sequence of data transfer regimes within a file
open regime; the data transfer regimes may group activity attribute.
each be for either read or write data transfer.
(amend rirle clause 7.3, page 4)
Write data transfer permits the operations insert,
replace or extend. 7.3 Object selection regime control
7.2 Filestore management (amend 1st paragraph, page 4)
(replace clause, page 4)
2

---------------------- Page: 4 ----------------------
IS0 857 1-3: 1988/Amd. 1 :I 992 (E)
(amend Figure 2, page 4)
FTAM regime
object selection regime
file open regime
F-READ F-TRANSFER-END
F-WRITE F-CANCEL
F-LOCATE
F- ERASE
F-OPEN F-CLOSE
F- READ-ATTR I B
F-READ-LINK-ATTRIB
F-CHANGE-AmRIB
F-CHANGE-LINK-AlTRIB
F-COPY
F-MOVE
.ECT
F-DES
F-SELECT
F- D ELETE
F-SELECT-ANOTHER
F-U N LI N K
F-CREATE
F-CREATE-DIRECTORY
F-LINK
F-GROUP-COPY
F-G ROU P-MOVE
F-GROUP-LIST
F-G ROU P-SELECT
F-G ROU P-D ELETE
F-G ROU P-CHANGE-AmRIB
F-CHANGE-PREFIX
F-LIST
F-TEF NATE
F-INITIALIZE
F-U-A 1RT
F-P-ABORT
Figure 2 - File service regimes and related primitives
3

---------------------- Page: 5 ----------------------
IS0 857 1 -3:1988/Amd.l :I 992 (E)
Eight services are associated with object selection
a) the read attributes service (see clause 16.1) is
regime control:
used by the initiator to interrogate the object
attributes of the selected object;
a) the object selection service (see clause 15.1) is
used by the initiator to select a specific object by
b) the change attributes service (see clause 16.2)
pathname and to bind the specified object to the is used by the initiator to modify the object
FTAM regime;
attributes of the selected object;
aa) the select another service (see clause 15.la) is c) the read reference attributes service (see
used by the initiator to bind a previously clause 16.3) is used by the initiator to interrogate
unselected file from the generalized selection the object attributes of the reference identified
group to the FTAM regime;
by the current pathname activity attribute;
b) the object deselection service (see clause 15.2) d) the change reference attributes service (see
is used by the initiator to release the binding clause 16.4) is used by the initiator to modify the
between the FTAM regime and the specified object attributes of the reference identified by
object; the current pathname activity attribute;
c) the file creation service (see clause 15.3) is
e) the move object service (see clause 16.5) is
used by the initiator either used by the initiator to place the currently
selected object into a specific file-directory by
1) to create a specified file and to select the
changing its primary pathname object attribute;
newly created file; or
f) the copy object service (see clause 16.6) is used
2) depending on the override parameter of
by the initiator to create a duplicate of the
F-CREATE, to select an existing file;
currently selected object in a specific file-
and then to bind the specified file to the FTAM directory.
regime;
NOTE - When accessing an object via a reference, the
Ca) the file-directory creation service (see move object and copy object services operate only on the
clause 15.3a) is used by the initiator to create a reference object, not the referent object.
specified file-directory object and bind the newly
7.6 Grouping control
created file-directory to the FTAM regime;
(append aiter 1 st paragraph, page 5)
cb) the reference creation service (see
clause 15.3b) is used by the initiator to create a
The set of primitives contained wiihin a group are
specified reference object and bind the existing
constrained as follows:
object to which it is linked to the FTAM regime;
a) FTAM regime control, filestore management and
d) the object deletion service (see Clause 15.4) is
generalized filestore service primitives will never
used by the initiator to release the binding
appear within a group;
between the FTAM regime and the specified
b) recovery and restait service primitives will never
object in such a way that the previously selected
appear within a group;
object ceased to exist;
c) data transfer regime primitives, including
e) the reference deletion service (see clause 15.5)
F-DATA, F-DATA-END, F-LOCATE and
is used to delete an existing reference, leaving
F-ERASE, will never appear within a group;
the object to which it was linked intact in the
filestore, and release the binding between the
d) if a regime is requested to be created and
FTAM regime and the linked object.
be terminated within a single
requested to
grouped sequence, then every regime requested
(amend title to clause 7.4, page 5)
to be created within the grouped sequence is
7.4 Object management
also requested to be terminated within that
grouped sequence;
(amend 1 st paragraph, page 5)
e) primitives may be present within a giwp only if
Six services are associated with object management:
they are allowed within the negotiated service
class, and the corresponding functional unit was

---------------------- Page: 6 ----------------------
IS0 857 1-3:1988/Amd.l:1992 (E)
negotiated during the FTAM regime
1 ) a single,optional, limited filestore management
establishment; procedure to change current name prefix or list
filestore;
1) any service from list 1 (below) must not appear
in the same grouped sequence with a service 2) a single grouped series of requests to establish
from list 2: a file open regime. (See clause 7.6 for valid
grouped sequences);
1) F-CREATE,
F-CREATE-D I RECTORY
3) a single bulk data transfer procedure, for either a
read transfer or a write transfer. The processing
2) F-READ-LINK-ATTRIBUTES
mode parameter on the F-OPEN primitive is set
F-CHANGE-LINK-ATTRIBUTES
to either a read or a valid write action, as defined
F-U N LI N K
in the constraint set, but not both.
'lause 12*2 and associated tables also
4) a single grouped series of requests to release
constraints on legal grouped sequences.
the file open and select regimes. (See clause
(append after clause 8. I. 6, page 6) 7.6 for valid grouped series.).
(delete note, page 6)
8.1.6a Limited filestore management
The limited filestore management functional unit 8.2.2 File access class
supports management of the current name prefix, and
(amend 1st paragraph, pages 6 and 8)
listing of objects within the filestore. In addition this
The file access class consists of:
functional unit supports the selection, deselection, and
interrogation of directory and reference attributes.
a) the kernel functional unit;
8.1.6b Enhanced filestore management
b) both of the read and write functional units;
The enhanced filestore management functional unit
c) the file access functional unit;
provides for the creation and deletion of file-directory
d) optionally, the grouping functional unit. If the
and reference objects, and the modification of
grouping functional unit is successfully
reference and directory object attributes.
negotiated, its valid use in any instance by the
8.1.6~ Object manipulation functional unit
initiator is optional but the acceptance by the
The object manipulation functional unit provides responder is always mandatory.
services to manage the position of objects within the
e) optionally, the limited file management functional
filestore, and to duplicate objects within the filestore.
unit;
8.1.6d Group manipulation functional unit
f) optionally, but only if the limited file management
The group manipulation functional unit provides for functional unit is present, the enhanced file
management functional unit;
identifying a group of files within the filestore,
interrogating the contents of that group, and for
fa) optionally, the limited filestore management
manipulation operations on that group of files.
functional unit;
8.2.1 File transfer class
fb) optionally, but only if the limited filestore
management functional unit is present, the
(amend 1 st paragraph, page 6)
enhanced filestore management functional unit;
ea) Optionally, the limited filestore management
fc) optionally, the object manipulation functional
functional unit;
unit;
(amend 2nd paragraph, page 6)
fd) optionally, but only if the object manipulation
In the file transfer service class, the use of the
functional unit is present, the group manipulation
services is constrained so that there is a sequence
functional unit:
of zero or more FTAM events on the application
association. Each FTAM event requested by the g) optionally, the FADU locking functional unit;
initiator is a series of requests consisting of:
h) optionally, in the internal file service, the
recovery functional unit;
I
5

---------------------- Page: 7 ----------------------
IS0 857 1-3: 1988/Amd. 1 : 1992 (E)
(append afier entry U6, page 71
Table 1 - Services and functional units of the External File Service
14a.1
change current name prefix
U6a Limited
14a.2
filestore list file-directory
15.1
management filedirectory selection
file-directory deselection 15.2
reference selection
15.1
reference deselection
15.2
read file-directory attributes
16.1
read reference attributes
16.3
J6b IWlanced file-directory creation
15.3a
filestore file-directory deletion
15.4
management reference creation
15.3b
reference deletion
15.5
change file-directory
16.2
attributes
16.4
change reference attributes
(requires 6a)
J6c Object move object 16.5
nanipulation copy object 16.6
14b.1
J6d Group generalized selection
14b.2
nanipuiation generalized deletion
group change attributes 14b.7
group move 14b.3
14b.5
group COPY
14b.6
group list
15.1a
select another
optionally, in the internal file service, the restart c) optionally, the enhanced file management
i)
functional unit:
data transfer functional unit.
(delete 2nd note, page 8) d) the grouping functional unit;
8.2.3 File management class e) optionally, the limited filestore management
functional unit;
(amend tst paragraph, page 8)
f) optionally, but only it the limited filestore
The file management class consists of:
management functional unit is present, the
enhanced filestore management functional unit;
a) the kernel functional unit:
b) the limited file management functional unit; g) optionally, the object manipulation functional
unit;
6

---------------------- Page: 8 ----------------------
IS0 857 1 -3:1988/Amd.l :I992 (E)
association. Each FTAM event is either;
h) optionally, but only if the object manipulation
functional unit is present, the group manipulation
a transfer comprising:
functional unit.
1 ) a single, optional, limited filestore management
(amend 2nd paragraph, page 8)
procedure to change current name prefix or list
In the file management service class the use of the
filestore;
services is constrained so that there is a series of zero
2) a single grouped series of requests requested
or more FTAM events on the application association.
by the initiator to establish a file open regime.
Each FTAM event requested by the initiator is a single
(See clause 7.6 for valid grouped series).
grouped series of requests. (See clause 7.6 for valid
sets of grouped primitives.) The file management a single bulk data transfer procedure, for either
3)
class imposes the following further restrictions on a read transfer or a write transfer. The
grouped primitives: processing mode parameter on the F-OPEN
primitive is set to either a read or a valid write
a) The F-OPEN and F-CLOSE primitives are
action, as defined in the constraint set, but not
excluded from use;
both.
b) if a grouped series of primitives establishes a
4) a single grouped series of requests requested
select regime, it must also terminate the select
by the initiator to release the file open and select
regime.
rdgimes. (See clause 7.6 for valid grouped
8.2.4 File transfer and management class series.)
or a single grouped series of requests requested by
(amend Ist paragraph, page 8)
the initiator to effect management. (See clause 7.6 for
The file transfer and management class consists of:
valid grouped sequences.) The open regime will not
be entered. If the select regime is established within a
a) the kernel functional unit;
grouped series, then it will also be terminated within
b) the grouping functional unit;
the grouped series of requests.
c) one or both of the read or write functional units;
(delete the node, page 8)
d) the limited file management functional unit;
e) optionally, the enhanced file management
functional unit;
ea) optionally, the limited filestore management
(append after table 3, page 9)
functional unit;
limited filestore limited filestore
eb) optionally, but only if the limited filestore
management management
management functional unit is present, the
enhanced filestore management functional unit;
enhanced filestore enhanced filestore
management management
ec) optionally, the object manipulation functional
unit;
ed) optionally, but only if the object manipulation
fdnctional unit is present, the group manipulation
functional unit;
f) optionally, in the internal file service, the restart
data transfer function unit;
g) optionally, in the internal file service, the
recovery functional unit.
(amend 2nd paragraph, page 8)
In the file transfer and management service class, the
use of the services is constrained so that there is a
repeated series of FTAM events on the application
7

---------------------- Page: 9 ----------------------
IS0 857 1-3: 1988/Amd.l:1992 (E)
Section two: Definition of file service primitives
12.2 Constraints on the issue of primitives Lfmg limited filestore management functional
unit
(amend 1st paragraph, pages 11 & 14; this includes
Efmg enhanced filestore management
the list of grouped sequences)
functional unit
The primitives may be issued in any sequence
consistent with the constraints given in tables 7 to 10. G-Lfmg grouping and limited filestore
The sequences of primitives are defined under the management functional units
individual services. Individual series of requests
grouping and enhanced filestore
G-Efmg
requested by the initiator may be interleaved to form
management functional units
7.6 for valid groups.
grouped sequences. See clause
Obmn object manipulation functional unit
(amend the notes, page 14)
G-Obmn grouping and object manipulation
NOTES
functional units
1) Not all sequences are allowed in the file transfer, file
group manipulation functional unit
Grmn
management, and file transfer and management
classes (see clauses 8.2.1, 8.2.3, 8.2.4). In these classes,
G-Grmn grouping and group manipulation
the threshold parameter is set so that the sequences
functional units
either succeed or fail as a whole, i.e. set to the number
(insert after 1st paragraph, page 14)
of primitives between the begin group and end group
primitives.
Tables 9 and 10 assume that completion of a
previous file service event implies that all functional
2) Other constraints will affect the ability of the file service
user or file service provider to invoke the various units required by the corresponding file service
procedures, such as flow control constraints on sending
primitive were negotiated.
data or constraints on the ability of a file service user to
(insert after clause 12.3.2, page 14)
accept spontaneous F-P-ABORT indications from the
file service provider.
12.3.3 Notes from tables 9 and 10
12.3.2 Conventions for tables 9 and 10
Il] This transition is only allowed if no regimes other
than the FTAM regime are currently established.
(amend 1st paragraph, page 14)
[2] This transition is only allowed if the select regime
In tables 9 and 10, the entries indicate the functional
is the innermost regime established.
units required for the succession to occur. The entries
are: [3] This transition is only allowed if the open regime is
the innermost regime established.
Kernel kernel functional unit
12.4 Confirmed services
Grouping grouping functional unit
(amend 2nd paragraph, page 20)
Lmgt limited management functional unit
A request to establish a new regime (F-INITIALIZE,
Emgt enhanced management functional unit
F-SELECT, FSELECT-ANOTHER, F-CREATE,
Recover recover functional unit F-CREATE-DIRECTORY, F-LINK OR F-OPEN) may
be rejected by use of a response with state result
Access file access functional unit
parameter indicating failure (see clause 13.1 ).
G-Lmgt grouping and limited file management
functional units
G-Emgt grouping and enhanced
management functional units
8

---------------------- Page: 10 ----------------------
IS0 8571-3:1988/Anid.l:1992 (E)
8
8 8
8
m
8
8
8
,8
8 8
State result
Action result
Attributes
Requested access
Referent indicator
initiator
F-SELECT Yes
Access passwords
Concurrency control ’
Shared ASE information
Account
Diagnostic

---------------------- Page: 11 ----------------------
IS0 8571-3:1988/Amd.l:1992 (E)
(append to table 6, pages 11 and 12)
Table 6 - File service primitives
'-CHANGE-PREFIX Initiator Action result
Yes
Reset
Destination file-directory
Access passwords
Diagnostic
Initiator
F-LIST Yes
&!lSCtLe%lLe assertions
E& asswords
Attributznames
Objects attributes list
Diaanostic
Initiator 4ction result
'-GROUP-SELECT Yes
State result
4ttribute value assertions
qequested access
3co e
4c& passwords
0
:oncurrency control
Maximum set size
îccount
Shared AS€ information
Diagnostic
Initiator Action result
Yes
'-GROUP-DELETE
Charging
Request operation result
O eration result
dared ASE information
P-COPY yes initiator
Destination file-directory
Override
Error action
Create password
Access passwords
Attributes
Request operation result
Operation result
Diagnostic
Initiator Action result
F-GROUP-MOVE Yes
Destination file-directory
Ferrida rrora ion
Create assword
Attribut&
Request operation result
Operation result
Diagnostic
Action result
Yes Initiator
F-GROUP-LIST
Attribute names
Objects attributes list
Diagnostic
F-GROUP-CHANGE- Initiator Action result
Yes
Attributes
ATTR I B
Error action
SE information
bared
âiagnostc
Yes Initiator State result
F-SELECT-ANOTHER
Action result
Last member indicator
Shared ASE information
pferent indicator
IC
iagnos

---------------------- Page: 12 ----------------------
IS0 857 1 -3:1988/Amd.l :I 992 (E)
(append to table 6, pages 11 and 12)
Table 6 (continued) - File service primitives
Initiator State result
f -CREATE-DIRECTORY Yes
Action result
Attributes
Create password
Requested access
Shared ASE information
Account
Diagnostic
Initiator State result
F-LINK Yes
Action result
Attributes
Target object
Create password
Requested access
Access passwords
Concurrency control
Shared ASE information
Account
Diagnostic
Action result
Yes Initiator
F-U N LI N K
Shared ASE information
Charging
Diagnostic
Action result
Yes Initiator
F-READ-LINK- ATTRI6
Attribute names
Attributes
Diagnostic
Yes Initiator Action result
F-CHANGE-LINK-ATTRIB
Attributes
Diagnostic
Initiator Action result
Yes
F-COPY
Destination file-directory
Override
Create password
Access passwords
Attributes
Diagnostic
Action result
Yes Initiator
F-MOVE
Destination file-directory
Override
Create password
Access passwords
Attributes
Diagnostic
11

---------------------- Page: 13 ----------------------
IS0 857 1 -3:1988/Amd.l :I992 (€1
(amend Figure 3, page 13)
recover
FTAM regime establishment Regime establishment - file transfer class
change current name prefix
list file-directory ,
generalized select
list generalized selection group
move
generalized
generalized change- attribute
select another
create director
change link attribute
File regime establishment -file access class
Figure 3 - Simplified State Diagram for successful activity (see Annex E)
12

---------------------- Page: 14 ----------------------
IS0 857 1-3:1988/Amd.l :I 992 (E)

---------------------- Page: 15 ----------------------
IS0 8571-3:1988/Amd.l:1992 (E)
3
a
E
.-
c,
c
Y 8
ti
c,
Q
.-
c,
.-
E
.-
I
U)
.- E
P
L
8
rc
.-
.e
E
.-
P
al
O
‘2
%
Yi
O
al
O
5
a
ua
I
U2
al
14

---------------------- Page: 16 ----------------------
IS0 857 1-3:1988/Amd.l :I 992 (E)
15

---------------------- Page: 17 ----------------------
IS0 857 1 -3:1988/Amd.l:1992 (E)
16

---------------------- Page: 18 ----------------------
IS0 857 1 -3:1988/Amd.l :I992 (E)
mg .-
En
L
Q)
O
2
Q)
v)
Q)
E
ô
Q)
O
C
Q)
J
a$
I
17

---------------------- Page: 19 ----------------------
.- E
En
2
O
‘E
3
al
z
ô
Yi.
O
-2
al
v)
Yi
O
al
o
c
al
3
v)
I
UJ
al
$

---------------------- Page: 20 ----------------------
is0 8571 -3:1988/Amd.l :I992 (E)
19

---------------------- Page: 21 ----------------------
IS0 857 1 -3: 1 988/Amd. 1 : 1992 (E)
.-
m
L
$
>
.-
c,
.-
E
.-
P
aa
O
‘E
Q
v)
*
O
aa
O
C
aa
a
U
aa
v)
I
Q)
aa
20

---------------------- Page: 22 ----------------------
IS0 857 1-3:1988/Amd.l :I992 (E)
3
J
C
.-
c,
C
F!
Y
I
O
'2
3
al
E
L
O
*
al
O
'E
3
*
O
I
Q)
.
al
,
j
i
, I
t
i
t
L
f
i
I
I
c
i
r
I
z
l
(
I
1
21

---------------------- Page: 23 ----------------------
IS0 8571-3:1988/Amd.l:1992 (E)
22

---------------------- Page: 24 ----------------------
IS0 857 1-3:1988/Amd.l: 1992 (E)
23

---------------------- Page: 25 ----------------------
~ IS0 8571-3:1988/Amd.l:1992 (E)
3
a
C
.-
c,
C
v 8
ài
'z1
C
O
Q
2
I
al
E
L
O
rc
24

---------------------- Page: 26 ----------------------
IS0 857 1 -3:1988/Amd.l :I992 (E)
5
U
C
O
5:
L
.f
E
.-
er,
2
O
2
B
Q)
E
O
w-
.- 5
c,
.-
E
.-
ô.
w-
O
I
$
Q)
25

---------------------- Page: 27 ----------------------
IS0 857 1-3: 1988/Amd. 1:1992 (E)
26

---------------------- Page: 28 ----------------------
IS0 857 1-3: 1988/Amd.l :I992 (E)
27

---------------------- Page: 29 ----------------------
~ IS0 8571-3:1988/Amd.l:1992 (E)
I
.- !
O>
E
al
O
‘E
al
U)
al
E
8
rc
al
O
5
?T
28

---------------------- Page: 30 ----------------------
IS0 857 1 -3:1988/Amd.l :I992 (E)
I
.E .-
cn
L
O
'E
Q)
v)
r
O
al
O
S
v)
29

---------------------- Page: 31 ----------------------
IS0 857 1-3: 1988/Amd. 1: 1992 (E)
30

---------------------- Page: 32 ----------------------
IS0 857 1 -3:1988/Amd.l :I 992 (E)
31

---------------------- Page: 33 ----------------------
IS0 8571 -3:1988/Amd.l :I992 (E)
a
a
32

---------------------- Page: 34 ----------------------
IS0 857 1-3:1988/Amd.l :I992 (E)
2) The pathname specified on create actions will not
13 Common file service parameters
necessarily be the primary pathname of the object
13.5 Attributes being created.
(amend 1st paragraph, page 20)
(amend
...