ISO 8571-4:1988/Amd 2:1993
(Amendment)Information processing systems — Open Systems Interconnection — File Transfer, Access and Management — Part 4: File Protocol Specification — Amendment 2: Overlapped access
Information processing systems — Open Systems Interconnection — File Transfer, Access and Management — Part 4: File Protocol Specification — Amendment 2: Overlapped access
Extends the protocol specifications given in ISO 8571 part 4 and supporting the internal and external file service interfaces to provide support for 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 4: Spécification du protocole de fichiers — Amendement 2: Chevauchement d'accès
General Information
Relations
Standards Content (Sample)
INTERNATIONAL
IS0
STANDARD
8571-4
First edition
1988- 1 O-O 1
AMENDMENT 2
1993-08- 15
Information processing systems - Open Systems
Interconnection - File Transfer, Access and
Management -
Part4:
File Protocol Specification
AMENDMENT 2 : Overlapped access
Systemes de traitement de /‘information - Interconnexion de systbmes
ouverts - Transfert, accks et gestion de fichiers -
Partie 4 : Spkcification du protocole de fichiers
AMENDEMENT 2 : Chevauchement d’accirs
Reference number
IS0 8571-4:1988/Amd.2:1993 (E)
---------------------- Page: 1 ----------------------
IS0 8571.4:1988/Amd.2:1993 (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
of International Standards through technical committees
development
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 2 to International Standard IS0 8571-4:1988 was prepared by Joint
Technical Committee lSO/IEC JTC 1, information technology.
IS0 8571 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 1993
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.
lSO/IEC Copyright Office l Case postale 56 l CH-1211 Gen&ve 20 l Switzerland
Pri nted in Switzerland
---------------------- Page: 2 ----------------------
IS0 857%4:1988/Amd.2:1993 (E)
- Open Systems Interconnection - File
Information processing systems
Transfer, Access and Management -
Part 4:
File Protocol Specification
AMENDMENT 2 : Overlapped access
other BDT actions, subject to restrictions; this is called
0. Introduction
conseclJtiv8 access. secondly, read and write actions can
be perfomed in parallel, so that both directions of data
Ciause 0 provides an introduction to this amendment. The
transfer are exploited at any one time. Requests are then
text in this clause iS not intended for inclusdon in IS0 $571
taken from the queue whenever either direction of transfer
part 4.
becomes free. This is called concurrent access.
The transfer of a single FADU, specified in a single F-READ
0.1 General
request has the same interpretation as in Iso 8571. The
resultant effect on the virtual filestore of a set of overlapped
IS0 8571 part 4 provides specifications of the protocols that
requests using consecutive access shall be the same as
support the internal and external file service interfaces.
that of the equivalent set of requests issued in series; the
service provided is serializable. If concurrent access is
This amendment extends these protocol specifications to
used then the resultant effect of a set of write actions on the
provide support for the services offered by overlapped
virtual filestore, is also serializable. However, due to the
access.
non-determinism introduced by the use of concurrent
access, lt is also possible that in some uses of the service,
the data transferred as a resutt of a read action is not
0.2 Rationale
consistent with the current state of the file.
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
1. scope
operations; the serial nature of the current FTAM data
transfer services introduces a significant control overhead
This amendment makes no additjons to clause I.
if the FADUs are small. In this context, an FADU is small if
its transmission time is comparable with the time to complete
a confirmed service on the association (the association’s
2. Field of application
round trip delay).
This amendment makes no adMions to clause 2.
0.3 Summary
The current design envelope that there should be at most
3. References
one file selection per association and one file open per file
selection is maintained. If access to more than one file is to
This amendment makes no additions to clause 3.
be overlapped, more than one association is necessary,
The overlapped access takes place within a constant set of
presentation contexts established as at present when the file
4. Definitions and abbreviations
is opened, or previously.
Two different degrees of overlap have been identified.
This anwdnent makes no additions to clause 4.
Firstly, requests for future accesses may be issued whilst a
previously requested BDT action is in progress, allowing the
creation of a queue of read and write requests. In general,
PCI relating to a given BDT action may be overlapped with
---------------------- Page: 3 ----------------------
IS0 857%4:1988/Amd.2:1993 (E)
Section one: General
5. Overview of the protocol
516 Protocol functional units
52 Services assumed by the basic file
protocol
Add to end of list.
Amend table 1.
k) consecutive amess functional unit
I) concurrent access functional unit
TAM Session Presentation
unctional Unit Functional Unit Functional Unit
J
Kernel Kernel
Duplex Duplex
Optionally: Optionally:
Resynch( 1) Resynch( 1)
Minor synch(2) Minor synch(2)
Context Management(3)
Minor Synch Minor Synch
Svmmetric Synchronize (5) Svmmetrii Svnchronize (54
Minor Synch Minor Synch
Resynchronize Resynchronize
Symmetric Synchronize (5) Symmetric Synchronize (5;
NOTES
5 The Symmetric Synctuonize functiod unit is used when overlapped acc0ss is in use. Pending the specification of presentation symmetric
synchronisation services, recovery mechanisms will not be available for use during ovdapped access.
2
---------------------- Page: 4 ----------------------
IS0 857%4:1988/Amd.2:1993 (E)
Section two: Basic file protocol
6.2.6 Transfer number
6. State of the association provided
In overlapped xcess, the transfer number identifies the
62 Additional state information
bulk data transfer within a sequence of transfers from one
data transfer idle stat0 to a n8xt data transfer idle stat8 within
62.3 Next state indicator
an open regime. tt is set to zero at each data tmskr idle
state.
Replace second sentence.
two transfer numbers are
In concurrent overlapped access,
The defined values are the state names “initialised”,
maintained - one for reads and one for writes.
“selected”, “normal data transfer idle”, “consecutive data
transfer idle”, “concurrent data transfer idle”, and “unset”.
7. File protocol data units
6.2.5
This amendment makes no ack%tions to clause 7.
Add as last
paragraph:
8. File initiating entity actions
In overlapped access, the bulk transfer number identifies
the bulk data transfer that can be cancelled, restarted or
recovered. Thus, the bulk transfer number is incremented
only when there is an outstanding data transfer request and
9. File responding entity actions
the previous data transfer cannot be cancelled, restarted or
recovered. If an initiator and a responder have different bulk
transfer numbers then it is the bulk data transfer associated
with the smaller of the two numbers that is cancelled,
10. File general actions
restarted or recovered.
This amendment makes no additions to ckws0 10.
---------------------- Page: 5 ----------------------
IS0 857%4:1988/Amd.2:1993 (E)
Section three: The basic bulk data transfer protocol
bulk data transfer, and by error recovery mechanisms. The
11. State of bulk data transfer activity
value is incremented when a checkpoint is made. The value
is an integer in the range 1 to 999998. Initially, the value is
#b-label slJklalJse 11.2.
determined by the state of the association.
11.2 Additional state of the entities (without
The ch8ckpoint identifier expected mi8s only to FOAM
overlapped access)
regimes for which the us8 of the restart and/or recovery
ucc8ssfuJly negotiated.
functional units have been s
Replace first paragraph.
11.3A First next synchronisation point number
The following sub-clauses define the items of stat8
information associated with the basic protocol entities for
The first next synchronisation point number reflects the
th8 purposes of bulk data transfer without overlapped
s8quenc8 of events In th8 supporting synchronisation
access.
s8rvic8s for a sender. The number is the se&l number of the
next session synchronisation point to be issued by the
session service provider. The value is an integer in the
Add the following sub-clauses.
range 0 to 999998. Initially on a newly created session
connection, the value is 1.
11.3 Additional state of the entities (with
consecutive access) The first next synchronisation point number applies only to
WAM regimes for which th8 us8 of the presentation
symmetric synchronisation functional unit has been
The foliowing sub-clauses define the items of state
successfully negotiated.
information associated with the basic protocol entities for
th8 purposes of bulk data transfer with consecutive access.
11.3.5 Second next synchronisation point
11.3.1 Current Transfer Number number
The current transfer number indicates the transfer number of
The second next synchronisation point number refleds the
the bulk data transfer procedure that is currently considered
s8quenc8 of events in the supporting synchronisation
“in progress”.
services for a receiver. The number is the serial number of
the next session synchronisation point to be issued by the
11.3.2 Start Bulk Transfer Number session service provider. The value is an integer in the
rang8 0 to 999998. Initially on a newly created session
connection, the value is 1.
The start bulk transfer number indicates the bulk transfer
number of the first In a sequence of overlapped data
The second next synchronisation point number applies only
transfers. The start bulk transfer number is used to calculate
to FOAM regimes for which the us8 of the presentation
the bulk transfer number and transfer number for cancel,
symmetric synchronisation functional unit has been
recover and restart.
successfully negotiated.
11.3.3 Checkpoint identifier expected
The checkpoint identifier expected reflects th8 sequence of
checkpoints within bulk data, and is reset by the start of the
Table 5 - Protocol Data Units
Name Carried by Functional units
F-CHECK rquest P-SYNC-MINOR request recovery, r8start
(see note 2)
F-CHECK response P-SYNC-MINOR response recOV8ry, restart
(see note 2)
NOTES
1 The data value corresponds to an F-DATA request service primitiw. There is no F-DATA request PDU as S&L
2 If overlapped acc8ss is not in use then the F-CHECK request and response p&nitives are mapped &ectJy onto the P-SYNC-MINOR rquest and
rwponse primitiv8& with no aciditional syntax.
4
---------------------- Page: 6 ----------------------
IS0 8571.4:1988/Amd.2:1993 (E)
11.3.6 Synchronisation offset The read and write &e&point tab&s (two separate tabbs
are kept) n%ord checkpointing information for each
The synchronisation offset is a constant established when ongoing bulk data transf8f. The following infofmatkm is kept
for each currently active bulk data transfer: transfer number,
a read or wriie bulk data transfer is initiated or recovered,
checkpoint expected,
which gives the difference between the checkpoint bulk transfer number,
identifier exp8cW and the next resynchmnisation point synchronisatbn offset, and &e&point counter. The size of
th8 table is that of the transfer window negotiated When the
number.
fib is opened.
The synchronisation offset applies only to FTAM regimes
for which use of the presentation symmetric synchronisation 11,3.14 Last trm end confirm hdimm
functional unit has been successfully negotiated.
The last transfer end confirm indicator records the last
NOTE - Except during the issue of a &e&point, or performance of the
transfer end received by the initiator. The bst transfer end
restart procedure the value of the synchronisation offset is equal to the
confirm received is sent to the responder on a transfer end
difference between the expected &e&point number and the next
request PDU. It is also included on cancel, recover and
syrstwonisation pointnumber.
restart PDlJs. The responder uses the Information in
removing items from the transfer end response queue and
11.3.7 Outstanding Checkpoint counter
in th8 re-issuing of transfer-end response after a session
resynchronisation in the diredion of responder to initiator.
the number of
The outstanding checkpoint counter records
checkpoints which are unacknowledged.
11.3.15 bst transfef end indkation indicator
11.3.8 Read/Write indicator
The last transfer end indication indicator records the last
transfer 8nd indication received by the responder. tt iS
The read/write Indicator records whether the current bulk
inch&d on cancel, recover and restart PDUs. The initiator
data transfer is to or from the initiator. The value is set upon
us8s the information in the r8-issuing of transfer 8nd
the beginning of the data transfer regime. The defined
requests after a session resynchronisation in the direction
values are “reading”, “writing” and “unset”. The initial
of initiator to responder.
value Is unset.
11.3.9 Discard Indicator
11.4 Additional state of the entities (with
concurrent acc0ss)
The discard indicator is us8d to signal that data received
during cancellation or before recovery ls invalid and should
The following sub-clauses define the items of state
be thrown away. tf the recovery or restart functional units
information associated with the basic protocol entities for
are selected and presentation resynchronisation functional
the purpos8s of bulk data transfer with concurrent acmss.
unit has been s ucc8ssfuily negotiated, it is used in
conjunction with session resynchronisation to producs a
11.4.1 Current Read Transfer Number and
recovery without us8r visibility of the error; otherwise it is
Current Write Transfer Number
us8d during the cancel phase. The defined values are
“unset” and “set”. Initially, th8 value is “unset”.
The current transfer read number and the current transfer
writ8 number indicate the transfer numbers of the read and
11.3.10 Transfer Request Queue
write data transfer procedures that are in progress.
The transfer request queue records the transfer number and
11.42 Stem Bulk Transfer Number
transfer type (read or write) of all outstanding data transfers.
The start bulk transfer number indicates the bulk transfer
11.3.11 Transfer End Queue
number of th8 first in a sequence of overlapp8d data
transfers. The start bulk transfer number Is used to calculate
The transfer end queue records the transfer numbers of all
the bulk transfer number and transfer number for cancel,
data transfers, already recorded on th8 transfer request
recover, and restart.
queue, for which a transfer end PDU request or response
has been issued.
llA3 checkpoint identifier expected
11.3.12 Data End Queue
The ch8ckpoint identifier 8xp8ct8d refeeds the sequence of
checkpoints within bulk data, and is reset by the start of the
The data 8nd queue records th8 transfer numbers of all data
bulk data transfer, and by error recovery mechanisms. The
transfers, already recorded on th8 data request queue, for
value is incremented when a checkpoint is made. The value
which a data end PDU has been issued or received.
11.3.13 Read and write checkpoint tables
---------------------- Page: 7 ----------------------
IS0 857%4:1988/Amd.2:1993 (E)
checkpoints which are unacknowledged.
ls an Integer In the range 1 to 999998. Initially, the value is
determined by the state of the association.
llA.8 Read Indicator and Write hdicator
The checkpoint identifier exp8ctgd applies only to FTAM
regimes for which the use of the restart and/or recovery
The read indicator and the write indicator record whether or
functional units have been s uccessfuliy negotiated.
not there aI’ r8ad Or Writ8 data transfers in progress. The
defined WiU8S ar8 “r8&i~‘?-WIiti~” and “UnS& Th8
11AA First next synchronisation point number
initial value is unset
The first next synchronisation point number reflects the llA.9 Discard indicator
s8quence of events in the supporting synchronisation
services for a sender. The number is the serial number of the
The discard indicator is used to signal that data received
next session synchronisation point to be issued by the
during Canceilation or before r8covery is invtiid and shoukj
session service provider. The value is an integer in the
be thrown away. tf the recovery or restart fUndiod Units
range 0 to 999998. Initially on a newly created session
are s8l8cted and presentation resynchronisation functional
connection, the value is 1.
unit has been s ucc8ssfuiiy negotiated, it is us8d in
conjunction with session resynchronisation to produc8 a
The first next synchronisation point number applies only to
recovery without us8r visibility of the error; otherwise it is
FTAM regimes for which the us8 of th8 presentation
used during the cancel phase. The defined values are
functional unit has been
symmetric synchronisation
“uns8t” and %8tH. initially, the value is “unset”.
successfully negotiated.
llA.10 Transfer Read Request Queue d
11.4.5 Second next synchronisation point
Transfer Write Request Queue
number
The transfer read request queue and the transfer writ8
The second next synchronisation point number reflects the
request queue record th8 transfer numbers of all
sequence of events in the supporting synchronisation
outstanding read and write data transfers.
services for a receiver. The number is the serial number of
th8 next session synchronisation point to be issued by the
llA.11 Transfer End Read Queue and
session service provider. The value is an integer in the
Transfer End Write Queue
range 0 to 999998. Initially on a newly created session
connection, the value is 1.
The transfer end read queue and the transfer 8nd Writ8
qU8U8 record the tfansf8r numbers of all read and Writ8 data
The second next synchronisation point number applies only
transfers, already recorded on th8 transfer request read
to RAM regimes for which the us8 of the presentation
(wriie) queue, for which a transfer end PDU requ8st or
symmetric synchronisation functional unit has been
response has been issued.
successfully negotiated.
11.4.12 Data End Read clueue and Data End
11.4.6 Synchronisation offset
Write Queue
The synchronisation offset is a constant established when
The data end read queue and the data end writ8 queue
a read or write bulk data transfer is initiated or recovered,
record th8 transfer numbers of all read and write data
which gives the difference between the checkpoint
transfers, all ready recorded on the transfer request read
identifier expected and the next resynchronisation point
(wriie) queue, for which a data end PDU has been issued/
number.
received.
The synchronisation offset applies only to FTAM regimes
llA.13 Read and write checkpoint tables
for which use of the presentation symmetric synchronisation
functional unit has been succxssfully negotiated.
The read and write checkpoint tables (two separate tables
are kept) record checkpointing information for 8ach
NOTE - Except during the issue of a checkpoint, or performance of the
ongoing bulk data transfer. The following information is kept
restart procedure the value of the synchronisation offset is equal to the
for each currently active bulk data transfer. transfer number,
difference between the expected &e&point number and the next
syrd-mnisatjon point number. bulk transfer number, checkpoint expected,
synchronisation offset, and checkpoint counter. The size of
1 lA.7 Outstanding Checkpoint counter
the table is that of the transfer window negotiated when the
file is opened.
The outstanding checkpoint counter records th8 number of
llA.14 Last transfer end confirm indicator
The last transfer end confirm indicator recOrdS the ht
6
---------------------- Page: 8 ----------------------
IS0 857%4:1988/Amd.2:1993 (E)
transfer end read (write) received by the initiator. The last 13. Bulk data transfer initiating entity
transfer end confirm received is sent to the responder on a
actions
transfer end request PDU. tt is also included on cancel,
recover and restart PDUs. The responder uses the
information in removing items from the transfer end response
queue and in the re-issuing of transfer-end response after
14. Bulk data transfer responding entity
a session resynchronisation in the direction of responder to
actions
initiator.
11.4.15 Last transfer end indication indicator
15. Bulk data transfer sending entity
The last transfer end indication indicator r8cords the last
actions
transfer end read (write) indication received by the
responder. It is included on cancel, recover and restart
PDUs. The initiator uses the information in the re-issuing of
transfer end requests after a session resynchronisation in
16. Bulk data transfer receiving entity
the direction of initiator to responder.
actions
12. Bulk data transfer protocol data
units
17. Bulk data transfer general actions
Amend table 5.
---------------------- Page: 9 ----------------------
IS0 8571.4:1988/Amd.2:1993 (E)
Section four: The error recovery protocol
19. Specification of the error control
1 em Protocol mechanisms
protocol
8
---------------------- Page: 10 ----------------------
IS0 8571.4:1988/Amd.2:1993 (E)
Section five: Abstract Syntax
20. Abstract Syntax Definition
21, Application Context Name
73is ammdinent ma&es no addtbns to Claus0 21.
20.3 AsN.1 uodule Definition
Amend F&urn 7.
22. Conformance
Amend FgUre 8.
This amendment makes no additions to &use 22.
Amend F@ure 9.
Amend Figure 10.
'SO8571-FTAM DEFINITIONS ::=
EGIN
Functional-Units ::= [4] IMPLICIT BIT STRING
read
I ( a,
write
( 31,
file-access
( 4),
limited-file-management
( 5),
enhanced-file-management
( 61,
grouping
( 71,
fadu-locking
( 81,
recovery
( 9,
restart-data-transfer
(lo),
limited-filestore-management
(11) I
enhanced-filestore-management
(12) I
object-manipulation
(13),
group-manipulation
(14),
consecutive-access
(151,
concurrent-access
(16) 1
:ND
Figure 7 - FWU regime PDUs
9
---------------------- Page: 11 ----------------------
IS0 8571-4:1988/Amd.2:1993 (E)
S08571-FTAM DEFINITIONS ::=
EGIN
F-OPEN-request ::= SEQUENCE {
processing-mode [O] IMPLICIT BIT STRING
{ f-read
(0) I
f-insert (1) I
f-replace (2) r
f-extend
(3),
f-erase (4) } DEFAULT { f-read ),
contents-type [l] CHOICE {
unknown [O] IMPLICIT NULL,
proposed [l] Contents-Type-Attribute },
concurrency-control Concurrency-Control OPTIONAL,
shared-ASE-information Shared-ASE-InformationOPTIONAL,
enable-fadu-locking [2] IMPLICIT BOOLEAN DEFAULT FALSE,
activity-identifier Activity-Identifier OPTIONAL,
- Only used in the recovery functional unit.
recovery-mode [3] IMPLICIT INTEGER
t none UN,
at-start-of-file (l),
at-any-active-checkpoint (2) ) DEFAULT none,
remove-contexts [4] IMPLICIT SET OF Abstract-Syntax-Name OPTIONAL,
define-contexts [5] IMPLICIT SET OF Abstract-Syntax-Name OPTIONAL,
- The following are conditional on the negotiation of the consecutive overlap or
- concurrent overlap functional units.
degree-of-overlap Degree-Of-Overlap OPTIONAL,
transfer-window [7] IMPLICIT INTEGER OPTIONAL }
F-OPEN-response ::= SEQUENCE {
state-result
State-Result DEFAULT success,
action-result Action-Result DEFAULT success,
contents-type [l] Contents-Type-Attribute,
concurrency-control
Concurrency-Control OPTIONAL,
shared-ASE-information
Shared-ASE-InformationOPTIONAL,
diagnostic
Diagnostic OPTIONAL,
recovery-mode
[3] IMPLICIT INTEGER
1 none (W,
at-start-of-file (l),
at-any-active-checkpoint (2) } DEFAULT none,
presentation-action
[6] IMPLICIT BOOLEAN DEFAULT FALSE,
- This flag is set if the responder is going to follow this response by a P-ALTER-CONTEXT
-
exchange.
- The following are conditional on the negotiation of the consecutive access or
- concurrent access functional units.
degree-of-overlap Degree-Of-Overlap OPTIONAL,
transfer-window
[7] IMPLICIT INTEGER OPTIONAL )
Figure 8 - File selection and file open regime PDlJs
10
---------------------- Page: 12 ----------------------
IS0 8571-4:1988/Amd.2:1993 (E)
F-RECOVER-request ::= SEQUENCE {
activity-identifier Activity-Identifier,
bulk-transfer-number [O] IMPLICIT INTEGER,
- If concurrent access was in use then this parameter indicates the read bulk
-
transfer.
requested-access Access-Request,
access-passwords Access-Passwords OPTIONAL,
recovery-point [2] IMPIIICIT INTEGER DEFAULT 0,
- zero indicates beginning of file point after last checkpoint indicates end of file
[3] IMPLICIT SET OF Abstract-Syntax-Name OPTIONAL,
remove-contexts
define-contexts [4] IMPLICIT SET OF Abstract-Syntax-Name OPTIONAL,
- The following are conditional on the negotiation of overlapped access.
concurrent-bulk-transfer-number [7] IMPLICIT INTEGER OPTIONAL,
-
conditional on use of concurrent access
[8] IMPLICIT INTEGER OPTIONAL,
concurrent-recovery-point
- conditional on use of concurrent access. Zero indicates beginning of file
- point after last checkpoint indicates end of file
last-transfer-end-read-response [9] IMPLICIT INTEGER OPTIONAL,
[lo] IMPLICIT INTEGER OPTIONAL }
last-transfer-end-write-response
F-RECOVER-response ::= SEQUENCE {
state-result State-Result Default success,
action-result Action-Result DEFAULT success,
contents-type [l] Contents-Type-Attribute,
recovery-point [2] IMPLICIT INTEGER DEFAULT 0,
- Zero indicates beginning of file; point after last c? leckpoint indicates end of file
diagnostic Diagnostic OPTIONAL,
presentation-action [6] IMPLICIT BOOLEAN DEFAULT FALSE,
- This flag is set if the responder is going to follow this response
- by a P-ALTER-CONTEXT exchange.
- The following are conditional on the negotiation of overlapped access.
concurrent-recovery-point [8] IMPLICIT INTEGER OPTIONAL,
-
conditional on use of concurrent access. Zero indicates beginning of file; point after
- last checkpoint indicates end of file
last-transfer-end-read-request [9] IMPLICIT INTEGER OPTIONAL,
last-transfer-end-write-request [lo] IMPLICIT INTEGER OPTIONAL )
Figure 8 (continued) - File selection and file open regime PDUs
11
---------------------- Page: 13 ----------------------
IS0 857%4:1988/Amd.2:1993 (E)
Amend F&we 9.
S08571-FTAM DEFINITIONS ::
EGIN
F-READ-request ::= SEQUENCE {
file-access-data-unit-identity FADU-Identity,
access-context Access-Context,
fadu-lock FADU-Lock OPTIONAL,
- The following is conditional on the negotiation of consecutive of concurrent access.
transfer-number [0] IMPLICIT INTEGER OPTIONAL )
F-WRITE-request ::- SEQUENCE {
file-access-data-unit-operation [O] IMPLICIT INTEGER
{ insert
(0) I
replace
(1) I
extend
(2) 1,
file-access-data-unit-identity FADU-Identity,
FADU-Lock OPTIONAL,
fadu-lock
- The following is conditional on the negotiation of consecutive or concurrent access.
[l] IMPLICIT INTEGER OPTIONAL )
transfer-number
F-TRANSFER-END-request ::= SEQUENCE {
shared-ASE-information Shared-ASE-InformationOPTIONAL,
- The following are conditional on the negotiation of consecutive or concurrent access.
Request-Type OPTIONAL,
request-type
transfer-number [0] IMPLICIT INTEGER OPTIONAL,
last-transfer-end-read-response [l] IMPLICIT INTEGER OPTIONAL,
last-transfer-end-write-response [2] IMPLICIT INTEGER OPTIONAL )
F-TRANSFER-END-response ::- SEQUENCE {
action-result Action-Result DEFAULT success,
shared-ASE-information Shared-ASE-InformationOPTIONAL,
diagnostic Diagnostic OPTIONAL,
- The following are conditional on the negotiation of consecutive or concurrent access.
request-type Request-Type OPTIONAL,
transfer-number [0] IMPLICIT INTEGER OPTIONAL )
F-CANCEL-request ::= SEQUENCE {
action-result Action-Result DEFAULT success,
shared-ASE-information Shared-ASE-Information OPTIONAL,
diagnostic Diagnostic OPTIONAL,
- The following are conditional on the negotiation of consecutive or concurrent access.
request-type Request-Type,
transfer-number [0] IMPLICIT INTEGER OPTIONAL,
last-transfer-end-read-request [l] IMPLICIT INTEGER OPTIONAL,
last-transfer-end-read-response [2] IMPLICIT INTEGER OPTIONAL,
last-transfer-end-write-request [3] IMPLICIT INTEGER OPTIONAL,
last-transfer-end-write-response [4] IMPLICIT INTEGER OPTIONAL }
F-CANCEL-response ::= SEQUENCE (
action-result Action-Result DEFAULT success,
shared-ASE-information
Shared-ASE-InformationOPTIONAL,
Figure 9 - Bulk data transfer PDUs
12
---------------------- Page: 14 ----------------------
IS0 857%4:1988/Amd.2:1993 (E)
diagnostic Diagnostic OPTIONAL,
- The following are conditional on the negotiation of consecutive or concurrent access.
request-type Request-Type OPTIONAL,
transfer-number [O] I
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.