ISO 8571-3:1988/Amd 1:1992
(Amendment)Information processing systems — Open Systems Interconnection — File Transfer, Access and Management — Part 3: File Service Definition — Amendment 1: Filestore Management
Information processing systems — Open Systems Interconnection — File Transfer, Access and Management — Part 3: File Service Definition — Amendment 1: Filestore Management
Amends Introduction, clauses and subclauses 6.2, 6.3, 7.3, 7.4, 7.6, 8.1.6, 8.2.1 to 8.2.4, 12.2, 12.3.2, 12.4, 13.5 to 13.8, 14.1.2.12, 15, 15.1.1, 15.1.2, 15.1.2.3, 15.1.2.8, 15.1.2.9, 15.2.1, 15.3.2.3, 15.3.2.5, 15.4.1, 15.4.2, 15.4.2.1, 15.4.2.3, 16, 16.1.1, 16.1.2, 16.1.2.2, 16.2.1, 16.2.2, 16.2.2.2, A.6, tables 1, 6, 9, 10, figures 3, 13, 15, annexes B, E, adds subclauses 12.3.3, 13.14 to 13.25, 14a, 15.1a, 15.3a, 15.5, 16.3 to 16.6, figures 12a, 14a.
Systèmes de traitement de l'information — Interconnexion de systèmes ouverts — Transfert, accès et gestion de fichiers — Partie 3: Définition du service de fichiers — Amendement 1: Gestion du système de fichiers
General Information
Relations
Standards Content (Sample)
INTERNATIONAL
IS0
STANDARD
857 l-3
First edition
1988-10-01
AMENDMENT 1
1992-12-15
Information processing systems - Open Systems
Interconnection - File Transfer, Access and
Management -
Part3:
File Service Definition
AMENDMENT 1 : Filestore Management
Technologies de l’information - lnterconnexion de systkmes ouverts (OS/) -
Transfert, acc& et gestion de fichiers -
Partie 3: Dbfinition du service de fichiers
AMENDEMENT 1: Gestion du systhme de fichiers
-- - ___
- -
= =
= TLE
= =
= =
= =
Z Z
I
Y
E =
=
s
Z
Ei =
Reference number
=. z=z
Z
E
!E
- -
- ~
IS0 8571-3:1988/Amd.l:1992 (E)
---------------------- Page: 1 ----------------------
IS0 857%3:1988/Amd.1:1992 (E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the International
Eiectrotechnicai 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 lSO/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 7 : General introduction
- Part 2 : Virtual Filestore Definition
- Part 3 : File Service Definition
- Part 4 : File Protocol Specification
- Part 5 : Protocol Implementation Conformance Statement Proforma
0 lSO/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.
0
ISO/IEC Copyright Off ice Case postale 56 l CH-1211 Gen&ve 20 l Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
IS0 8571-3:1988/Amd.1:1992 (E)
Information processing systems - Open Systems
Interconnection - File Transfer, Access and Management -
Part3:
File Service Definition
AMENDMENT 1 : Filestore Management
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.
0 Introduction (amend 4th paragraph, page I)
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 systems.
management. It also specifies a protocol available
IS0 8571 does not specify the interfaces to a file
within the application layer of the Reference Model.
transfer, access or management facility within the local
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%3:1988/Amd.l:1992 (E)
Section one: General
6.2 File service levels Eight services are associated with filestore
manaaement:
u
(amend 1 st paragraph’s item (a), page 3)
the change current name prefix service (see
a)
the external file service (EFS), in which the user
a)
clause 14a. 1) 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
b)
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
attribute value assertion list in or under a file-
there is no visibility of recoverable errors or the
directory;
error recovery actions;
6.3 Regimes of the file service the generalized selection service (see clause
4
14b. 1) 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 to a given attribute value
assertion list;
the FTAM regime, existing while the application
a)
the group deletion service (see clause 14b.2) is
association is used for the FTAM protocol,with
d)
used by the initiator to remove the file objects
which a group of file object complete pathnames
identified by pathnames in the generalized se-
is associated;
lection group such that the objects cease to
the object selection regime during which a
b)
exist.
particular object is associated with the FTAM
the group move service (see clause 14b.3) is
regime;
e)
used by the initiator to transfer the file objects
the file open regime during which a particular set
C)
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
f )
the data transfer regime during which a
d)
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
9)
by the initiator to interrogate the pathnames of
The file service provides for:
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
h)
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.
read or write data transfer.
each be for either
(amend title clause 7.3, page 4)
Write data transfer permits the operations insert,
7.3 Object selection regime control .
replace or extend.
(amend 1st paragraph, page 4)
7.2 Filestore management
(replace clause, page 4)
---------------------- Page: 4 ----------------------
IS0 857%3:1988/Amd.l:1992 (E)
(amend Figure 2, page 4)
FTA M reaime
object selection regime
file open regime
data transfer regime
F-DATA-END
F-READ F-TRANSFER-END
F-WRITE F-CANCEL
F-LOCATE
F-ERASE
F-CLOSE
F-OPEN
F-READ-A-TTRIB
F-READ-LINK-Al-l-RIB
F-CHANGE-A-ITRIB
F-CHANGE-LINK-ATTRIB
F-COPY
F-MOVE
F-DESELECT
F-SELECT
F-DELETE
F-SELECT-ANOTHER
F-UNLINK
F-CREATE
F-CREATE-DIRECTORY
F-LINK
F-GROUP-COPY
F-GROUP-MOVE
F-GROUP-LIST
F-GROUP-SELECT
F-GROUP-DELETE
F-GROUP-CHANGE-AlTRIB
F-CHANGE-PREFIX
F-LIST
F-TERMINATE
F-INITIALIZE
F-U-ABORT
F-P-ABORT
Figure 2 - File service regimes and related primitives
3
---------------------- Page: 5 ----------------------
IS0 8571-3:1988/Amd.l:1992 (E)
Eight services are associated with object selection the read attributes service (see clause 16.1) is
a)
regime control: used by the initiator to interrogate the object
attributes of the selected object;
the object selection service (see clause 15.1) is
a)
used by the initiator to select a specific object by the change attributes service (see clause 16.2)
b)
is used by the, initiator to modify the object
pathname and to bind the specified object to the
FTAM regime; attributes of the selected object;
the select another service (see clause 15.1 a) is the read reference attributes service (see
a@ C)
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 WAM regime; by the current pathname activity attribute;
the change reference attributes service (see
the object deselection service (see clause 15.2)
b) d)
clause 16.4) is used by the initiator to modify the
is used by the initiator to release the binding
between the FTAM regime and the specified object attributes of the reference identified by
object; the current pathname activity attribute;
the file creation sewice (see clause 15.3) is the move object service (see clause 16.5) is
e)
C)
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
the copy object service (see clause 16.6) is used
f )
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-
directory.
and then to bind the specified file to the FTAM
regime;
NOTE - When accessing an object via a reference, the
the file-directory creation service (see move object and copy object services operate only on the
Ca)
reference object, not the referent object.
clause 15.3a) is used by the initiator to create a
specified file-directory object and bind the newly
7.6 Grouping control
created file-directory to the FTAM regime;
(append after 1st paragraph, page 5)
the reference creation service (see
Cb)
clause 15.3b) is used by the initiator to create a
The set of primitives contained within 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
the object deletion service (see clause 15.4) is
d) 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 restart sewice primitives will never
object in such a way that the previously selected
appear within a group;
object ceased to exist;
regime primitives, including
c) data transfer
the reference deletion sewice (see clause 15.5)
e)
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.
requested to be terminated within a single
grouped sequence, then every regime requested
(amend tit/e 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 1st paragraph, page 5)
e) primitives may be present within a group only if
Six services are associated with object management:
they are allowed within the negotiated sewice
class, and the corresponding functional unit was
---------------------- Page: 6 ----------------------
IS0 857%3:1988/Amd.1:1992 (E)
negotiated during the regime 1) a single,optional, limited filestore management
FTAM
establishment; procedure to change current name prefix or list
filestore;
f) 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-DIRECTORY 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-UNLINK
in the constraint set, but not both.
Clause 12.2 and associated tables also place
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.1.6, page 6) 7.6 for valid grouped series.).
8.1.6a Limited fllestore management (delete note, page 6)
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
functional unit supports the selection, deselection, and The file access class consists of:
interrogation of directory and reference attributes.
the kernel functional unit;
a)
8.1.6b Enhanced filestore management
both of the read and write functional units;
W
The enhanced filestore management functional unit
the file access functional unit;
Cl
provides for the creation and deletion of file-directory
modification of
and reference objects, and the optionally, the grouping functional unit. If the
d)
reference and directory object attributes. functional unit is successfully
grouping
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
optionally, the limited file management functional
9
filestore, and to duplicate objects within the filestore.
unit;
8.1.6d Group manipulation functional unit
optionally, but only if the limited file management
f )
The group manipulation functional unit provides for functional unit is present, the enhanced file
identifying a group of files within the filestore, management functional unit;
interrogating the contents of that group, and for
optionally, the limited fiiestore management
fa)
manipulation operations on that group of files.
functional unit;
8.2.1 File transfer class
but only if the limited filestore
optionally,
fb)
management functional unit is present, the
(amend 1st paragraph, page 6)
enhanced filestore management functional unit;
ea) Optionally, the limited filestore management
functional unit; optionally, the object manipulation functional
fc)
unit;
(amend 2nd paragraph, page 6)
optionally, but only if the object manipulation
fd)
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 FTAIVI’ events on the application
optionally, the FADU locking funciional unit;
association. Each FTAM event requested by the
9)
initiator is a series of requests consisting of:
optionally, in the internal file service, the
h)
unit:
recovefv functional
---------------------- Page: 7 ----------------------
IS0 8571,3:1988/Amd.1:1992 (E)
(append affer entry US, page 7)
Table I- Services and functional units of the External File Service
14a.l
change current name prefix
U6a Limited
o 0 0 0 0
14a.2
filestore list file-directory
file-directory selection 15.1
management
file-directory deselection 15.2
reference selection 15.1
reference deselection
15.2
read file-directory attributes
16.1
read reference attributes 16.3
U6b Enhanced
file-directory creation
15.3a
filestore
file-directory deletion 0 0
0 0 15.4
management reference creation
15.3b
reference deletion
15.5
change file-directory
16.2
attributes
16.4
change reference attributes
(requires 6a)
U6c Object move object 0 0 0 0 16.5
manipulation
copy object 16.6
U6d Group generalized selection 0 0 0 0
14b.l
14b.2
manipulation generalized deletion
14b.7
group change attributes
14b.3
group move
14b.5
group COPY
group list 14b.6
15.1a
select another
optionally, the enhanced file management
optionally, in the internal file service, the restart
Cl
1)
functional unit;
data transfer functional unit.
the grouping functional unit;
(delete 2nd note, page 8)
d)
optionally, the limited filestore management
8.2.3 File management class
e)
functional unit;
(amend 1st paragraph, page 8)
optionally, but only if the limited filestore
f )
The file management class consists of:
functional unit is present, the
management
enhanced filestore management functional unit;
a) the kernel functional unit;
b) the limited file management functional unit; optionally, the object manipulation functional
9)
unit;
6
---------------------- Page: 8 ----------------------
IS0 857%3:1988/Amd.1:1992 (E)
optionally, but only if the object manipulation association. Each FOAM event is either;
h)
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 sd 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
3) a single bulk data transfer procedure, for either
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.
regimes. (See clause 7.6 for valid grouped
8.2.4 File transfer and management class series .)
(amend 1st paragraph, page 8) or a single grouped series of requests requested by
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
the kernel functional unit; be entered. If the select regime is established within a
a)
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)
the limited file management functional unit;
d)
e) optionally, the enhanced file management
functional unit;
optionally, the limited filestore management
W
(append after tab/e 3, page 9)
functional unit;
limited filestore
eb) optionally, but only if the limited filestore
limited filestore
management
management functional unit is present, the management
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
functional 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 sewices is constrained so that there is a
repeated series of FTAM events on the application
---------------------- Page: 9 ----------------------
IS0 857%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 1 I & 14; this includes
the list of grouped sequences) Efmg filestore management
enhanced
functional unit
The primitives may be issued in any sequence
consistent with the constraints given in tables 7 to IO. G-Lfmg and limited filestore
grouping
The sequences of primitives are defined under the
management functional units
individual services. individual series of requests
G-Efmg grouping and enhanced filestore
requested by the initiator may be interleaved to form
management functional units
grouped sequences. See clause 7.6 for valid groups.
Obmn object manipulation functional unit
(amend the notes, page 14)
manipulation
G-Obmn grouping and object
NOTES
functional units
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 manipulation
group
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
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 7 4)
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
[l] 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, F-SELECT-ANOTHER, F-CREATE,
recover functional unit
Recover 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
---------------------- Page: 10 ----------------------
IS0 857%3:1988/Amd.l:1992 (E)
Table 6, page 11 modify as follows:
m
m m
n
n
n
m
H m
State result
Action result
Attributes
Requested access
Referent indicator
F-SELECT Initiator
Yes
Access passwords
Concurrency control
Shared ASE information
Account
Diagnostic
9
---------------------- Page: 11 ----------------------
IS0 8571.3:1988/Amd.l:1992 (E)
(append to table 6, pages 11 and 12)
Table 6 - File service primitives
Initiator Action result
F-CHANGE-PREFIX Yes
Reset
Destination file-directory
Access passwords
Diagnostic
F-LIST Yes Initiator
k&$%&e assertions
Sco e
Act ss asswords
&
Attribut 8 names
Objects attributes list
Diaonostic
Initiator Action result
F-GROUP-SELECT Yes
State result
Attribute value assertions
Requested access
Scope
Access passwords
Concurrency control
Maximum set size
Account
Shared ASE information
Diagnostic
Initiator Action result
Yes
F-GROUP-DELETE
Charging
Request operation result
0 eration result
SKared ASE information
Destination file-directory
Override
Error action
Create password
Access passwords
Attributes
Request operation result
Operation result
Diagnostic
Yes Initiator Action result
F-GROUP-MOVE
. .
. .
De&xz&innftle-directory
Create assword
Attribut B s
Request operation result
Operation result
Dragnostic
Initiator Action result
F-GROUP-LIST Yes
Attribute names
Objects attributes list
Diagnostic
F-GROUP-CHANGE- Initiator Action result
Yes
Attributes
AT-TRIB
Error action
pgreA&$E information
Bg
Initiator State result
F-SELECT-ANOTHER Yes
Action result
Last member indicator
Shared ASE information
pferent indicator
lagnos ~c
10
---------------------- Page: 12 ----------------------
IS0 857%3:1988/Amd.1:1992 (E)
(append to table 6, pages 77 and 72)
Table 6 (continued) - File service primitives
F-CREATE-DIRECTORY Initiator State result
Yes
Action result
Attributes
Create password
Requested access
Shared ASE information
Account
Diagnostic
F-LINK Yes Initiator State result
Action result
Attributes
Target object
Create password
Requested access
Access passwords
Concurrency control
Shared ASE information
Account
Diagnostic
Initiator Action result
F-UNLINK Yes
Shared ASE information
Charging
Diagnostic
Initiator Action result
F-READ-LINK-AITRIB Yes
Attribute names
Attributes
Diagnostic
Initiator Action result
F-CHANGE-LINK-ATTRIB Yes
Attributes
Diagnostic
F-COPY Yes Initiator Action result
Destination file-directory
Override
Create password
Access passwords
Attributes
Diagnostic
Initiator Action result
F-MOVE Yes
Destination file-directory
Override
Create password
Access passwords
Attributes
Diagnostic
---------------------- Page: 13 ----------------------
IS0 857%3:1988/Amd.l:1992 (E)
(amend Figure 3, page 13)
recover
initialize terminate
I I
Regime establishment - file transfer class
FTAM regime establishment
change current name prefix
list file-directory
generalized select
list generalized selection group
generalized move
generalized copy
generalized de!ete
generalized change- attribute
select another 1 1
create 1 1 delete
recover
create directory ,
link
read attribute
change attribute
read link attribute
open close
change link attribute
Data Transfer locate
erase
File regime establishment - file access class
Figure 3 - Simplified State Diagram for successful activity (see Annex E)
12
---------------------- Page: 14 ----------------------
(amend Tables 9 and 70, pages 76 to 79)
Table 9 - Sequence of service primitives for file service regimes - initiator
I
F-CHANGE- F-GROUP- F-GROUP- F-GROUP- F-GROUP-
F-LIST
DELETE COPY .request MOVE.request
Previous file sefvice event PREFIX.request . request SELECT
.request .request
Grmn
a rmn
4
7
Grmn
ANGE-PREFlX.confirm Lfmg Lfmg Grmn Grmn
Grmn
.
;T.request
,
.
Lfmg
;T.confirm ! Lfmg
t
F-G
.
Lfmg _ Lfmg Grmn brmn Grmn Grmn
F-G OUP-SELECT.confirm (+ve)
Lfmg Grmn Grmn Grmn
F-G OUP-SELECT.confirm (-ve) Lfmg Grmn
F-c
F-G
F-G
F-GROUP-LIST.request
I
tirmn
F-GROUP-LlST.confirm Grmn
m m 1
F-GROUP-CHANGE-AlTRIBUTE.request
Wmn
F-GROUP-CHANGE-A-ITRIBUTE.confim7 Grmn
Lfw Lfmg Grmn
mn
3
I--5tLtG Wequest
4
F-SELECT.confirm (+ve) I I I I I I I
1 1
4
I
tirmn
Lfmg
Grmn Grmn
F-SELECT.confirm (-ve) Lfma Grmn
1
F-SELECT-ANOTHER.request
.
T-1
LECT-ANOTHEKconfirm (-ve) LW Grmn Grmn Grmn Grmn
Lfmg
ktA I t.request
W4TE.confirm (+ve)
tirmn
Grmn Grmn Grmn
I?ZTE.confirm kve\ Lfma Lfma
WITE-DIRECTORY.reauest 1 1 I I I I I
F-CREATE-DIRECTORY.adirm l+vel 1 I I I I I I
Grmn
F-CREATE-DIRECTORY .cdirm (-ve)
Lfmg Lfmg Grmn Grmn Grmn
F-LINK.confirm (+ve)
.
Lfmg Grmn Grmn Grmn
F-LlNK.confirm (-ve) Lfmg Grmn
1
ECT.request
4
m m m I . I
Grmn
Lfmg Lfmg Grmn Grmn Grmn
F-OESELECT.confirm
f
t-UtLt 1 t.request
1
Grmn
Grmn
F-OELETE.confirm Lfmrt Lfma Grmn Grmn
I
F-UNLINK.request
1
Grmn
F-UNLINK.confirm Lfmg LfmCJ Grmn Grmn Grmn
I !
1 1
F-READ-AlTRIBrequest
F-READ-AITRIB.confirm
t-m-WlKlE3.request
l
Pl-JANPF -
--I K\,.aL-I\, . . .Y. confirm
8
INK-mIB.request
---------------------- Page: 15 ----------------------
Table 9 - Sequence of service primitives for file service regimes - initiator (continued)
F-GROUP- F-GROUP- F-GROUP- F-GROUP-
F-CHANGE- F-LIST
SELECT COPY .request MOVE.request
PREFIX.request . request DELETE
Previous file service event
.request .request
F-READ-LINK-AlTRIB.confirm
m
F-CHANGE-LINK-AlTRIB.request
F-CHANGE-LINK-AlTRIB.confirm
F-COPY .request
F-COPY anfirm
. I
F-MOVE.request
F-MOVE.confirm
F-OPEN.request
F-OPEN.confirm (+ve)
F-OPEN.confirm (-ve)
F-CLOSE.request
F-CLOSE.confirm
I
F-BEGIN-GROUP.request
F-BEGIN-GROUP.confirm
F-END-GROUP.request
I
Grmn Grmn
Grmn Grmn
F-END-GROUP.confirm Lfmg Lfmg
1
F-RECOVER.request
F-RECOVER.confirm (+ve)
Lfmg Grmn Grmn Grmn
Lfmg Grmn
F-RECOVER.confirm (-ve)
Bulk data transfer
,
F-LOCATE.request
L
F-LOCATE-confirm
F-EFlASE.request
.
F-EFMSE.confirm
---------------------- Page: 16 ----------------------
IS0 8571-3:1988/Amd.l:1
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.