ISO 8571-3:1988/Amd 2:1993
(Amendment)Information processing systems — Open Systems Interconnection — File Transfer, Access and Management — Part 3: File Service Definition — Amendment 2: Overlapped access
Information processing systems — Open Systems Interconnection — File Transfer, Access and Management — Part 3: File Service Definition — Amendment 2: Overlapped access
Extends the service definition of the externally visible file transfer, access and management service given in ISO 8571 part 3 in an abstract way to incorporate the services offered by overlapped access. The objective in introducing overlapped access is to allow more efficient access to structured files when a single initiator has a need to perform many reading and updating operations.
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 2: Chevauchement d'accès
General Information
Relations
Standards Content (Sample)
INTERNATIONAL
ISO
STANDARD
857 l-3
First edition
1988- 1 O-O 1
AMENDMENT 2
1993-08- 15
Information processing Systems - Open Systems
Interconnection - File Transfer, Access and
Management -
Part3:
File Service Definition
AMENDMENT 2 : Overlapped access
Systemes de traitement de I’information - interconnexion de systkmes
ouverts - Transfer-t, acc& et gestion de fichiers -
Partie 3: Dbfinition du Service de fichiers
AMENDEMENT 2 : Chevauchement d’accks
Reference number
ISO 8571-3:1988/Amd.2:1993 (E)
---------------------- Page: 1 ----------------------
ISO 8571-3:1988/Amd.2:1993 (E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized System for worldwide
standardization. National bodies that are members of ISO or IEC patticipate in
the development of International Standards through technical committees
established by the respective organization to deal with particular fields of
technical activity. ISO and IEC technical committees collaborate in fields of
mutual interest. Other international organizations, governmental and non-
governmental, in liaison with ISO and IEC, also take patt in the work.
In the field of information technology, ISO 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 2 to International Standard ISO 8571-3:1988 was prepared by Joint
Technical Committee lSO/IEC JTC 1, Information technology.
ISO 8571 consists of the following Parts, under the general title lnformation
processing Systems - Open Systems lnterconnection - File Transfer, Access and
Management:
- Part 7 : General introduction
- Part 2 : Virtual Filestore Definition
- Part 3 : File Service Definition
- Pari 4 : File Protocol Specification
- Part 5 : Protocol Implementation Conformance Statement Proforma
0 ISO/IEC 1993
All rights reserved. No part of this publication may be reproduced or utilized in any form or by
any means, electronie or mechanical, including photocopying and microfilm, without
Permission in writing from the publisher.
ISO/IEC Copyright Office l Case postale 56 l CH-1211 Geneve 20 l Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
ISO 857%3:1988/Amd.2:1993 (E)
- Qpen Systems Interconnection - File
Information processing Systems
Transfer, Access and Management -
Part3:
File Service Definition
AMENDMENT 2 : Overlapped access
0 Introduction be overlapped, more than one association is necessary,
Th8 overlapped access takes place within a constant sst of
presentation contexts established as at present when th8 file
Claus8 0 provties an introduction to thnS amendment. The
is opened, or previously.
text in this clause is not intencbd for inclusion in /so 8571
Pa-9
Two different degrees of overlap have been identified.
Firstly, requests for future acc8sses may b8 issued whilst a
previously reqU8St8d BDT action is in progress, allowing the
0.1 General
creation of a queue of read and wriie requests. In general,
PCI relating to a given BDT action may b8 overlapp8d with
ISO 8571 part 3 defines in an abstract way th8 extemally
other BDT actions, subject to restriiions; this is called
visible file transfer, acc8ss and management Service.
consecutive access. Secondly, read and write actions tan
b8 performed in parauel, so that both cw8ctions of data
This amendment extends this service definition to
transfer am explokd at any one time. Fkquests am then
incorporate the Services offered by overlapped acc8ss.
taken from th8 queu8 whenever 8ithef dit’8CtiOn Of tMSf8r
b8comes free; this is cakd concurrent acmss.
02 Rationale
Th8 transfer of a singls FADU, sp8cified in a Single F-MAD
request has th8 sam8 interpr8taUon as in lS0 8571. Th8
The Obj8CtiV8 in introducing overlapp8d acc8ss is to allow
resuttant effect on th8 virtual filestore of a set of overlapped
more efficient acc8ss to structured fil8s when a sing18
requ8sts using consecutive access SM b8 th8 same a6
initiator has a need to perform many reading and updating
that of the equivalerrt Set of r8quests issu8d in ser&s; the
operations; the serial nature of the current FTw data
servlce pfovid8d is seMkabl8. lf concurrent acc8ss is
transfer Services introduces a significant control overhead
used th8n th8 resultant 8ffect of a set of writ8 adions on th8
if the FADUs are small. In this context, an FADU is small if
virtual fikstore, is also serializable. kbwever, due to the
its transmission time is comparable with th8 time to complete
non-determinism introduced by the us8 of concurrent
a confirmed Service on the association (the association’s
acmss, it is ako possibl8 that, in som8 us8s of the s8rvic8,
round trip delay).
the data transferred as a resuit of a read action is no0
consistent with the current state of the f ile.
0.3 Summary
1 Scope and field of application
The current design envelope that there should be at most
on8 file selection per association and one file open per file
selection is maintained. tf access to more than one file is to This amndment mabs no a&Wons to ckuse 1.
---------------------- Page: 3 ----------------------
ISO 857%3:1988/Amd.2:1993 (E)
4 Abbreviations
2 References
This amndm8nt mk8s no aMtions to clause 4.
This ammdmnt rmkes no adtions to Claus8 2.
5 Conventions
3 Definitions
This amndm8nt mkes no adtions to Claus8 5.
This amndment makes no adtions to ckuse 3.
---------------------- Page: 4 ----------------------
ISO 8571-3:1988/Amd.2:1993 (E)
Section one: General
6 Model of the file Service
6.2 File Service levels
Repkce second sentence of a):
7 Services of the film swvice
Transfer of fiie data is modelled in the extemal file Service
as error fr88 operations.
7.8 Bulk dab tmamtw
63 Regimes of the file service Re- subdum 7.8:
Bulk data tran#er Wers to tlw bansbr, optkwlly with
R8@2? f@M8 2.
checkpointing, of one or more file acc0ss data units (See
20.1). There arc nine additional swvices associated with
Repke d) and g):
bulk data transfer-.
d) the data transfer regime during which particular bulk data
a) the consecutive access senke may be requested by an
transfer specifications are in forc8.
initiator to allow the overlap of the protml control
information for read and write bulk data transfer procedures
g) a sequence of data transfer regimes within a file op
(See ISO 8571-1);
regim8; the data transfer regimes may 8ach b8 for either
read transfer, wriie transfer or both, if overlapped acwss is
b) the concurrent access senke may be rquested by an
in us8. Brite data transfer- permits the operations insert,
initiator to aliow the concufr8nt pqpssion of fead and
replace, or extend.
write bulk data transfer procedums ( (sm BC) 8571-1)
c) th8 r8ad bulk data servlc8 (se8 24.1) is used by the
Add note after last Paragraph:
initiator to initiate a bulk data transfer from the responder (in
fiYe stdectio22 nqghe
fHe open regime
data trandkr regime
I
F-RW 2,L,,R ’
- END
F-WRITE
F-CANCEL
F-LOCATE
F-ERASE
F-DATA
F-CLOSE
F-DATA-END
F -OPEN
-ATTRIBUTE
F-CHANGE-ATTRIBUTE
F-SELECT F-DESELECT
F-CREATE F-DELETE
Filestore manag3ment
F-TERMINA’
F-U-ABORT
F-P-ABORT
Figure 2 - File service regims and related primitivees
---------------------- Page: 5 ----------------------
ISO 857%3:1988/Amd.2:1993 (E)
Table 1 - Services and functional units of the Extemal File Service
sec not8
0
Ul 5 Consecutive acc8ss
Se8 note
Concurrent access 0
Ul6
the roie of Sender), to the initiator (in the rol8 of recgiver); AM entries to Table I and re-number entrles accordknglgly:
d) the write bulk data service (sec 24.2) ls used by the
Initiator to initiate a bulk data transfer from th8 initiator (in the Add note a#t8r Table, 1:
roh of Sender) to th8 r8sponder (in the roh of r8C8iV8r);
Note-the ciomecutiw 8ccess adconcurTentacc8st3~
U*alkWtheservices pwi&dbythedandwrite~un#s
8) the data unit transfer servic8 (sec 24.3) is used by the
tlobe~.Th0~ofoheo~~km~
sender to transmit bulk data;
withinthedefinitionsof idvidual wvices.
f) the end of data transfer servic8 (s88 24.4) is used by the
sender to indicat8 completion of the data transfer;
8.2Senkedasses
g) the end of transfer serv’ce (SW 24.5) is used by th8
822 File access class
initiator to tonfirm that the data transfer procedure is
complete;
Insert the fokwing Atems and re-label accordhgly:
h) th8 cancel data transfer- service (~88 24.6) is used by
either the Sender or th8 receiver to cancel a data transfer d) optionally, the consecutive acc8ss functional unit;
procedure. When overlapped aaxss is allowed 8ith8r
direction may be cancelled independently of the other. 8) optionally, th8 concurrent acc8ss functional unit;
7.10 Checkpointing and restarting
9 Levels of file service
Add sentence to end of b):
Repke Table 3 - Functional units in the file sewkes
lf overlapped access is in us8 then either direction of
Insertnote:
transfer may be restarted.
Note - Pendng the 2pckath of presentation symmetric
synchronisation senha3s, recov0ry mechanismswiM not be available
8 Functional units and Service classes for us0 during ovedappd access.
8.1 Functional units
A&i the following clauses:
Table 3 - Functional units in the file service
txtemal fl18 S8lVlC8 Internal f 118 sefwc8
8.1.15 Consecutive access functional unit
K8m8I K8m8I
Riad
Read
The consecutive access functional unit allows th8 overlap
Wlit8 Write
of read and write data transfer- procedures as defined in ISO
File acwss Fil8aCC8SS
85714.
Limited fil8 management Umbd file management
Enhanced file management En hancxd f il8 management
8.1.16 Concurrent access functional mit
Grouping Grouping
FADU lockbg
FADU bcking
The concurrent access functional unit allows the overlap of
R0COW~
read and write data transfer procedures as &fined in ISO
Restart data transfer
85714.
c0M8CUtiveXC8SS c0nsecutiV8WC8SS
Concurrent acc8ss Concurrent acc8ss
8.1.17 Service classes and functional units
---------------------- Page: 6 ----------------------
ISO 857%3:1988/Amd.2:1993 (E)
Th8 availability of th8 functional units, mad, wrik,
10 Negotiation of Service class, FTAIU
consecutive accass, cmcurrent access, fii8 access,
QoS and functional units
hited fii8 managemmt, enhanced fk management,
grouping and FADU bcking is controlled by the servkx
Amend third paragraph: dss wgotiated (sec Tabk 1 and 2).
---------------------- Page: 7 ----------------------
ISO 857%3:1988/Amd.2:1993 (E)
Section two : Definition of file Service primitives
13.12 File Access Data Uait kientity
11 File service primitives
AM note.
Amend entrbs in Table 6.
Note: if amcurrent access is in use tkm the FADU kbntifiers
previous,currenPandnextare~~tonnrhetherthe~isa
12 Sequence of primitives readcxawtit0.
Chis amendment makes no additions to chuse 12.
AM the following chuses:
13.14 Bulk Tmmfw Numbw
13 Common file Service parameters
The bulk transfer numb8r parameter is only visib& in the
13.8 Concurrency Control
internal fiI8 s8rvic8. The parameter is us8d to id8ntify a
particular bulk data transfer within an op8n r8gim8. If th8 us8
fbpiace fifih Paragraph: of concurrent access is negotiated when th8 file open
regim8 is establi~hed th8n the fit% read data transfer within
If FADU locking is negotiated the locks s8t at file open have an open regime is numbered 1, and subsequent read
the scope of the relevant bulk data transfer procedure. If tranSf8rs arc COM~CLJ~~V~~~ numbered. Similtiy, th8 fiI’St
overiapped access is not in us8 then this is equivalent to the write data transfer within th8 open r8gim8 is numb8r8d 1,
and subs8quent write transfers arc cons8cutive~y
bulk data transfer regime.
numb8r8d. tf OV8&ipp8d access is not negothted, or if
cOnS8CXJtiV8 access is negotiated, then read and write bulk
If overlapped acc8ss is in us8 then th8 scope of the FADU
transfers .are numbered consecutiveiy, starting from 1 for
locking is that of the read and write action.
the firSt bulk data tranSf8r procedUr8 i.8. th8f8 iS On8
Table 6 - File Service primitives
Parameters
-Primitive Conf irrn8d Request by
1
stat8 r8SUlt
Action r8sutt
Processing mod8
Contents typ8
&ICUtT8nCy control
F-OPEN Y8S Initiator Shar8d ASE information
En& FADU Iocking
Diagnostic
D8gr88 of OV8Iiap
Transfer window
[Activity identifier]
[R-VW -1
[State result
Action r8sutt
Activity id8ntifier
Bulk transfer numb8r
mlJ8St8d -
Initiator Access passwords
[F-RECOVER] Yes
Contsnts typ8
R8covery Point
Diagnosttic
Concurrmt bulk transfer numb8r
Concurrent recovery point
Last transfer end read r8qUBsf
Last transfer end r8ad response
La& transfer end Writ8 r8qU8st
Last transfer end writ8 response]
6
---------------------- Page: 8 ----------------------
ISO 857%3:1988/Amd.2:1993 (E)
numbering S8qU8nW. for the r8spond8r it indkabs th8 transfer numb8r of th8 last
write data transkr for which a F-TFWNSFER-END
indication has been receiv8d.
13.15 Transfer Number
The defautt vtiue 0 indicates that th8re am no outstan&g
F-TRANSFER-END mqwsts or indications to be issmd or
Ttw transfer number parameter ls conditional on the us8 of
received.
overlapped access. The parameter is used by the initiator
and responder to identify an uncompleted bulk data transfer.
The value of the Parameter is an integer. cf overlapped
13.19 hast transter end weite mspmw
acc8ss is not in us8, or consecutive acc8ss is in us8, th8n
overlapping read and write transfers arc consecutively
numbered, starting from 1. The value ls reset wh8n all Th8 Iast transfer end wrib r8spons8 parameter is only
outstanding f8qU8StS arc completed. visibleintheintemdfUeserv~,andiscond~ionalonthe
us8 of concurrent aamsforth8openregime.Thevalueof
Nota - The transfer number of a bulk data transfer may exceed the the paramets? is a transfer numb8f (s88 13.14). For th8
value of the transfer window (17.1.2.10) 8s the latter parameter
initiator it indicat8s the transfer numb8r of th8 last wfit8 data
constrains the maximum number of transfers that arc uncompleted at
transfer for which a F-TRANSFER-EbD tonfirm has tmn
any one time.
r8dv8d; for th8 msponder it indicates th8 transfer numk
of the last write data transferfor which a F-TRANSFER-END
response has b88n issued.
13.16 Last transfer end read request
The d8fault vab Z8rO indicat8s that thef8 W8 no
The last transfer end r8ad request pafanW8f is only viSibl8
outstanding F-TRANSFER-END responses or confirms to
in the internal file Service, and iS conditional On the us8 of
b8 issued or received.
overlapped access for the open regime. The value of the
parameter is a transfer number (sec 13.14). For the initiator
it indicates the transfer numb8f of the iast read data transfer
14 RAM regime control
for which a F-TRANSFER-END request has been issued;
for the responder it indicates the transfer numb8r of the last
This amendmmt makes no addflions to Claus0 14.
read data transfer for which a F-TRANSFER-END
indication has b88n received.
15 File selection regime control
The d8faul’t value 0 indicat8S that th8B ar8 no outstanding
F-TRANSFER-END requests or indications to be i~sued or
received.
This amendment makes no aMtbns to Claus43 15.
13.17 Last transfer end read response
16 File management
The last transfer- end read response parameter is only visible
This 2m0n&mnt makes no acUtions to chuse 16.
in the intefnal file Service, and is conditional on the us8 of
ov8flapped access for the open regime. The value of the
parameter is a transfer number (sec 13.13). For the initiator
17 File open regime control
lt indicat8S the transfer number of the last read data transfer
for which a F-TRANSFER-END tonfirm has been received;
fof the responder it indicates the transfer number of the last
Amend second sentence:
read data transie? for which a F-TRANSFER-END response
has been iSSu8d.
This r8gim8 estabktms th8 degr88 of overkipped access,
proc8sSing mod8, presentation contexts, and concumncy
The default value 0 indicates that th8B ar8 no outstanding
control for the data transfer- activity which is to be performed.
F-TRANSFER-END responses or confirms to be i~sued or
feCeiV8d.
17.1 File open servke
13.18 Last transfer end write request
17.1.1 Function
The last transfer end write request parameter is only visible
Amend &st sentence of fitst paragraph:
in the internal file Service, and is conditional on the us8 of
ov8flapped access for the open regime. The value of the
lt also establishes concurrency control, the d8grw of
parameter is a transfer number (See 13.14). For the initiator
overlapped anrrss and possbk prmng mcd8s.
it indicates the transfer number sf th8 last wriie data transfer
for which a F-TRANSFER-END request has been is~ued;
---------------------- Page: 9 ----------------------
ISO 857%3:1988/Amd.2:1993 (E)
17.1.2 Types of primitives and parameters The bulk transfer number is defined In 13.14. The parameter
indicates th8 bulk transfer proc0dur8 that is to b8 mver8d.
Replace entties in table 21.
lf concurrent acc8ss is in us8 then this parameter Takes the
VtiU8 of th8 r8ad tfanSf8r that is to b8 r8covered (th8 writ8
transfer In id8ntifi8d by the concurr8nt bulk transfer numb8r
A&l the following sub clauses and re-nun&er:
parameter). The defautt value 0 indicat8s that there is no
read buik transfer to be recovered.
17.12.9 Degree Of Overlap
Add the fo//owing ckue8s.
The degr88 of overlap parameter indicates the d8gf88 of
ov8flapp8d access f8qUir8d during the fil8 open r8gim8:
19.1-2 Reoovery Point
either no overlapped acc8ss (normal), consecutive acc8ss
or concurrent acc8ss.
Ad Last paragraph.
The degr88 of overlap available during the open f8gim8 is
n concumnt OV8rlapped acc8ss is in us8 th8n the
the lowest of the values offered by th8 initiator and
parameter is with r8sp8ct to th8 r8ad data transfer that is
responder. For the purposes of negotiation, the degr88s of
identified by the bulk data transfer number. tf the bulk
overlapped acc8ss ar8 rated as: concurrent acc8ss
transfer numb8r is 2810 then th8 r8covery point parameter
(high&), consecutive accxss, no overlapped acc8ss
shall tak8 th8 value Zero.
(low8St). This valu8 is us8d t0 s8t the cuff8nt degf88 Of
overlap attribute.
19.1.2.10 Concurrent Bulk Transfer Number
17.1.2.10 Transfer Window
The concurrent bulk transfer numb8r parameter- is
conditional on th8 selection of th8 concurrent -
The transfer window Parameter indicates the number of bulk
functiona unit and the degf88 of overiap (~88 17.1.2.9)
data transfers that may be uncompleted at any tim8. There
b8ing set to concurrent acxess. The parameter tak8s the
is an independent transfer window for reads and writes in
vaiue of a bulk transfer numb8r (defined in 13.14) and
concurrent access, although the value of the limit is the
id8ntifi8s th8 write transfer that is to b8 r8covered (See
Same, Oth8tWiS8 the transfer- window is for both reads and
19.1.2.4).
Wrii8S.
The d8fautt vaJu8 0 indicates that there ls no write bulk
The value of the transfer window is the lowest of th8 values
transfer to b8 r8cover8d.
offered by the initiator or responder.
19.12.11 Concurrent Recovery Point
18 Grouping control
The concurrent r8covery point parameter is conditionti on
Chis amendment makes no aokiitions to Claus8 18 of ISO
the CXMICXJ~8nt acc8~s functional unit and the d8gr88 of
8571 part 3.
OV8fhp (Se8 17.1.2.9) b8ing S8t t0 WnW~8nt aCC8S. Th8
parameter indicat8.s that r8covery is to a Point b8fof-8 the
Start of th8 writ8 bulk data transfer (valu8 zero), or to a
19 Recovery (Internal Service only)
checkpoint within the bulk data tranSfer, or to a point
following its completion (~88 not8). The recovery point is
within the write buik data transfer identified by the
19.1 Regime recovery
concurrent bulk transfer numb8r (~88 19.1.2.10); tf the write
bulk transfer numb8r Paramets? is Zero then the write
19.1.2 Types of primitives and parameters
tBCOV8v Point parameter shall tak8 the VtilJ8 Zero. Th8
r~~3ry point is determined by th8 entity which was
Repkice tabb 24.
receiving data at the tim8 of failure. Cons8qu8ntly the
parameter is required to b8 present on the response
19.1.2A Bulk Transfer Number
primitive.
Tabie 211 F-OPEN parameters
Degree of overlap
Conditional Conditional Conditional Conditional
0
(4
Transfer window
Conditional Conditional
Conditional Conditional
0
(-1
---------------------- Page: 10 ----------------------
ISO 8571-3:1988/Amd.2:1993 (E)
tf the concurrent bulk transfer number is Zero, the 19.12.15 Last Transfer SEnd wdte Response
concurrent recovery Point Parameter shall take the vatue
Zero.
The last transfer 8nd write response mt8r is defkd in
13.19. lt is only present on the request primitive, and
NOTE - Recovery to 8 point following a write bulk data transfer
therefor8 indicat8s th8 bulk transfer numb8r of the kst Writ8
completion is defined for the case where the receiver has received an
data transf8r for which a transfer 8nd read conflrm primitiv8
F-DATA-EN63 indication but the F-TRANSFER-EN0 exchange has
had been received by th8 initiator. It is only pres8nt if
not completed. In such a Situation it would be unnecessary to go back
recovery is to an open regim8 that had negotiated the us8
to the last confirmed checkpoint. The only requirement is for both
of concurrent access.
sender and receiver to have an agreed understanding of the
completion of the transfer. A value one larger than the highest
checkpoint number issued by the sender is used to indicate recovery
Repke TU 24.
after bulk data transfer.
19.1 SZ.12 Last Transfer End Read Request
20 Access to file contents
The last transfer end read request Parameter is defirwd in
20.1 Bulk data tmnsfer
13.16. It is only present on the response primitive, and
th8r8for8 indicates th8 bulk tranSf8r nUmb8r of th8 last read
Repke second paragrqh:
data transfer for which a transfer end read indication
primitive had been received by th8 responder. It is only
When ovwlapped access is not In w, these procedures
present if recovery is to an open regime that had negotiated
start and finish in a Single data transfer idk state, and so tan
the us8 of concurrent access.
be considered as a sekontained procedural unit, which is
primitiv8 in th8 definition of the remainder of th8 file servioe.
19.1213 Last Transfer End Read Response
tf OV8r@p@d aCC8SS is in us8 then these procedures may
be overlapped. lt is ther8fore not necessarily true that read
The last transfer end read response Parameter is defined in
and write procedures Start and finish in a data transfer Mle
13.17. lt is only present on the request primitive, and
state.
therefore indicat8s the bulk transfer number of the last read
data transfer for which a transfer 8nd read tonfirm primitiv8
had been received by the initiator. lt is only present if
21 Bulk data transfer service primitives
recovery is to an open regime that had negotiated the use
of concurrent access.
Repke Table 30.
19.1.2.14 Last Transfer End Write Request AM sentence to end of fowth pmzgtaph:
lf ov8rtapped access is in us8 then the Initiator and
The last transfer end write request parameter is defined in
responder may each be acting as both sender and receiver,
13.18. It is only present on the response primitive, and
with respect to the read and write procedures, as previously
therefore indicates the bulk transfer number of the last wnt8
described.
data transfer for which a transfer end read indkation
primktive had b88n received by the respond8r. lt is only
present if r~covery is to an open r8gim8 that had negotlated
the us8 of concurrent aazess.
---------------------- Page: 11 ----------------------
ISO 857%3:1988/Amd.2:1993 (E)
Table 24 - F-RECOVER parameters
,
F-RECOVER
Parameter F-RENNER F-RECOVER F-RECOVER
tonfirm ,
rewest indication r8scxxls8
uranaatory .
3fat8 H8SlJlI Ananaatofy
Mandatofy
ACtlOn f38SlJtt Mandatofy
Activity Mentif ier Mandatory Mandatory
( 1
Bulk Transfer Mandatory MandGory
=
number
( 1
Requested Access Mandatory Mandatory
( 1
3
Access Passwords 0ptio;al
I -VW Optional
Mandatory
Contents Type Mandatoty
( 1
Recovefy Point Condit ional Condit ional Conditional Conditknal
= =
( ) ( 1
Optional Optional
Diagnostic
. .
l . . . m .
Condltlonal Condltlonal Condrt ional
Concurrent Bulk Condit lonal
Transfer Number
( 1 ( 1
Concurrent Recovery Conditional Conditknal Conditional Conchonal
Point
( 1
Last Transfer End Conditional Condit hal
Read Request
Last Transfer End Conditional Conditional
=
Read Response
( 1
Last Transfer End Condltlonal Conditional
=
Wl’ii8 Request
( 1
Condit ronal
Last 1 ransfer tnd Condit ional
=
Wrii8 Response
( )
#
10
---------------------- Page: 12 ----------------------
ISO 8571.3:1988/Amd.2:1993 (E)
Section three: Definition of bulk data transfer primitives
of the bulk data tramfer servile with overtapped accms, ls
22 Sequence of bulk data transfer
specified in Annex F.
primitives
Note-Theuseofacommon DataTIWSWIdle~Dorreadand~~
22.1 Normal sequences bulkdatatransfer~resiclfigwe8,wstoYlusbatethe
progress of use of the bulk transfer sewice itself when ovdapped
access is not in use.
The normal progress of individual read and wriie bulk data
transfer procedures is iiiustrated by the state transition
Re-hbel figuri 8.
diagram shown in Figure 8. Fuil state transition diagrams arc
contained in Annex E.
Figure 8 - Simplified State Transition Diagram for Fkad and
Brite Buik Data Transfer Pmedures
The sequences of primitives aliow8d as a result of the us8
22.2 -m On issue of primitives
Tabk 30 - Bulk data transfer service primitives
\
Primitiv8 Conf irmed Reqwst Parameters Fahre
Name S8rvic8 Notkation
bY
F-READ No Initiator Bulk data transfer F-DATA-END
specification action mult
r&er f
F-WRITE No Initiator Bulk data transfer F-CANCEL
specification
Transfer number
er V&$
F-DATA-END No Sender Action result F-CANCEL
Diagnostic
F-TRANSFER-END Y8S Initiator Action result action result
Shared ASE information
Diagno&k
Requ=wP8
Transfer number
[Last transfer end read response)
[Last transfer end write response]
none
F-CANCEL Y8S Either Action result
Shared ASE information
Diagnostic
Requ=nP
Transfer number
[Last transfer- end read mquest]
Last tI’anSf8f 8nd read response]
[Last transfer end write request]
[Last transfer end write response]
F-CANCEL
[F-CHECK] Y8S Either [Checkpoint identifier
ransfer numberl
[F-RESTART] F-CANCEL
Y8S Eit her [Checkpoint identifier
Requ=t wpe
Transfer number
Last transfer end read request
Last transfer end read response
Last transfer end write request
Last transferend wriie response]
11
---------------------- Page: 13 ----------------------
ISO 8571-3:1988/Amd.2:1993 (E)
The primitives may be issued in any s8quence consistent Th8 F-Rm Se&8 Sp8cifi8S a data tGIIISf0f ffOm th8
with the LOTOS specification in Annex F. In addition, for the servic8 respondef (that is th8 aender) to th8 ~8rvic8 initiator
non-overiapped case, the constraints arc presented in (that is the receiv8r).
tables 31 and 32. The sequences given with the individual
primitive def initions apply.
24.1,l.l semke wimmt ove3rlapp0d acasa
Only one F-READ proc8dure may be in progress at any time
22.3 Key to tables 31 and 32
on a Single appücation -ion. The diredion of data
flow 8~tabMed continU8S until the exchange of F-
Chis amendment makes no changes to sub-clause 22.3. TRANSFER-END primitiv8S. Rej8ction sf an F-FEAD
indication is by ~SSU~ of an F-DATA-END with an action
resu# indicating u-Ul.
23 Common bulk data transfer
These prinatives Signal a transfer of control from the initiator
Parameters
to the sender. They mark a reversai of th8 service
asymmetry for the duration or the data transfer.
23.2 Checkpoint identifier
24.1.12 senrice with cmsecutive access
Repke last sentence of first paragraph:
lf the use of concurrent access has been negotiated for the
F-READ procedures may be requestecf at any time during
open regime then there may be more than one Checkpoint
the open regime, up to the ümit negotiated as the transfer
number sequence valid at any one time. The bulk transfer window when th8 open regime war 8~tabBShed. The
number is used to identify the correct sequence. For the F- requests for bulk transfer proc8dures ar8 queu8d by the
RESTART primitive, the value is between 0 and 999998 for responder. lf there arc no outstanding bulk transfer r8quBsfs
each direction of transfer.
then the F-DATA r8quBsfs may be i~~ued immediately,
oth8twiS8 th8 F-DATA requestt~ at-8 issued subj8ct to the
following constraints:
23.43 Request type
a) if the pr8c8ding bulk transfer proc8dur8 was a read
p~~1dUf8 th0n th8 ~pd8f fEiy i!%Ue F-DATA II3queStS
Th8 request type Parameter identifies the type of transfer to
after issuing th8 F-DATA-END request for the pr8c8ding
which a primitive is related i.e. read or wriie.
read procedure;
b) if the pr8c8ding bullc transfer proc8dure was a writs
24 Bulk data transfer
procedure then the responder may issue F-DATA requests
after issuing th8 F-TRANSFER-END response for that write
Repke the first Paragraph:
procedure.
Chis group of Services performs the transfer of bulk data.
A F-READ proc&~re concludes with th8 exchange of F-
Esch procedure begins with the servic8 initiator issuing
TRANSFER-END primitives.
8ither an F-READ request or an F-WRITE request as
appropriate. This ieads to the issue of a sequence of
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.