ISO 8571-4:1988/Amd 4:1992
(Amendment)Information processing systems — Open Systems Interconnection — File Transfer, Access and Management — Part 4: File Protocol Specification — Amendment 4
Information processing systems — Open Systems Interconnection — File Transfer, Access and Management — Part 4: File Protocol Specification — Amendment 4
Amends various clauses, removes subclause 6.2.4, adds new subclauses 8.3.1, 8.3.2, 20.5, and replaces annex A (Protocol state tables).
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 4
General Information
Relations
Standards Content (Sample)
INTERNATIONAL
ISO
STANDARD
8571-4
First edition
1988-10-01
AMENDMENT 4
1992-11-15
Information processing Systems - Open Systems
Interconnection - File Transfer, Access and
Management -
Part 4:
File Protocol Specification
AMENDMENT 4
Systkmes de traitement de I ’information - Interconnexion de systemes ouverts -
Gestion, acc& et transfert de fichier -
Partie 4: Spkification du protocole de transfert de fichier
AMENDEMENT 4
-
-
=
=
=
=
=
=
1
=
Y
Z
Z
= Z
=
=
Zl
-
z = Reference number
L@
ISO 8571-4:1988/Amd.4:1992 (E)
---------------------- Page: 1 ----------------------
ISO 857%4:1988/Amd.4:1992 (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 participate in the development of International Standards through
technical committees established by the respective organization to deal
with par-ticular 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
adopttid 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 4 to International Standard ISO 8571-4:1988 was prepared by
Joint Technical Committee lSO/IEC JTC 1, Information technology.
- 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 ISO/IEC 1992
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. CH-1211 Geneve 20 l Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
ISO 857%4:1988/Amd.4:1992 (E)
Information processing Systems - Open Systems
Interconnection - File Transfer, Access and Management -
Part 4:
File Protocol Specification
AMENDMENT 4
Page 6
Remove subclause 6.2.4.
Page 7
Modify the last sentence of clause 7 Paragraph 4 to read “The series of file protocol data units
may not be divided.”
Page 9
Add the following to subclauses 8.3.1 and 8.3.2 after the word “initialized ”:
II
. . . . where the requested access refers to a subset of the actions requested by the
sen/ice class and functional units negotiated at initialization,.”
Page 70
Remove from 8.3.3 the following:
“.where the requested access must refer to a subset of the actions requested,.”
Page 72
Remove subclause 8.9.3 item b.
---------------------- Page: 3 ----------------------
ISO 8571.4:1988/Amd.4:1992 (E)
Replace subclause 8.9.3 item c with the following text:
“lf the presentation action Parameter is false, issue an F-OPEN tonfirm primitive to the
IFS User, with Parameters derived from the data values received, and enter the state
“data transfer idle ”.”
Replace subclause 8.9.3 item d with the following text:
action Parameter is true, preserve the PDU
“If the presentation for further processing
II II
and enter state “p-al ter context pendin
9 ’
Remove subclause 8.9.4 item a.
Replace subclause 8.9.4 item b with the following text:
“If the presentation action Parameter is false, issue an F-OPEN tonfirm primitive to the
IFS User, with Parameters derived from the data values received;”
Replace subclause 8.9.4 item d with the following text:
“If the PDU did not carry a state result indicating failure and if the presentation action
Parameter is true, preserve the PDU for further processing;”
Change the last sentence of 8.9.5 first Paragraph from:
pending” and the p-alter indicator is set, the entity
“.in the “p-alter context
shall:.”
to:
and the presentation context management
“.in the state “p-alter context pending”
functional unit is available and there are presentation contexts to be deleted or defined,
the entity shall:.”
Add the word “Construct” at the beginning of 8.9.5 a). “Construct a presentation.”
Remove subclause 8.9.5 item d.
Change the last sentence of 8.9.6 first Paragraph from:
“.in the state “p-alter context pending” and the p-alter indicator is unset, the entity
shall:.”
to:
“.in the state “p-alter context pending” and the presentation context management
functional unit is available or there are no presentation contexts to be deleted or defined,
the entity shall:.”
Page 13
Remove subclause 8.13.2 item b.
---------------------- Page: 4 ----------------------
ISO 8571-4:1988/Amd.4:1992 (E)
Page 14
Replace subclause 8.13.2 item c with the following text:
“lf the presentation action Parameter is false, issue an F-RECOVER confirrn primitive to
the IFS User, with Parameters derived from the data values received, and enter the state
“data transfer idle recover ”.”
Replace subclause 8.13.2 item d with the following text:
“lf the presentation action Parameter is true, preserve the PDU for further processing
ff I’
and enter the state ” p-alter context pendi
ng o
Change the last sentence of 8.13.3 first Paragraph from:
“.in the state “p-alter context pending” and the p-alter indicator is set, the entity
shall:.”
to:
“.in the state “p-alter context pending” and the presentation context management
functional unit is available and there are presentation contexts to be deleted or defined,
the entity shall:.”
Remove subclause 8.13.3 item d.
Change the last sentence of 8.13.4 first Paragraph from:
“.in the state “p-alter context pending” and the p-alter indicator is unset, the entity
shall:.”
to:
“.in the state “p-alter context pending” and the presentation context management
functional unit is unavailable or there are no presentation contexts to be deleted or
defined, the entity shall:.”
Page 78
Replace “current PDU” with “current PSDU” in subclause 9.10.4 item a.
Page 79
Replace “F-RECOVER response primitive” with “F-RECOVER response Service primitive” in
subclause 9.13.2 item e.
Page 20
Replace “an action result Parameter” with “a diagnostic Parameter” in subclause 10.2 item a.
Page 2 I
Replace “presentation” with “Presentation” and “session” with “Session” in subclause 112.2
second sentence.
---------------------- Page: 5 ----------------------
ISO 857%4:1988/Amd.4:1992 (E)
with “‘Presentation” and “presentation” with “Presentation” in subclause
Replace “Session”
11.2.4
Page 22
Replace “next resynchronization Point number” with “next Synchronkation Point number” in
subclause 11.2.5 at the end of the first Paragraph.
Replace “presentation” with “Presentation” in subclause 11.2.5.
Replace “next synchronization Point serial number” with “next synchronization Point number”
in subclause 13.1.2 b).
Page 24
In subclauses 15.1.2 and 15.2.2 replace “P-SYNCH-MINOR” with “P-SYNC-MINOR ”.
Replace “next synchronization Point serial number” with “next synchronization Point number”
in subclause 15.3.1 item e.
Replace both occu rrences “next synchronization Point serial number” with
“next
I’
synchronization Point number in subclause 15.3.1 item f.
Replace “synch Point serial number” with “synchronization Point serial number” in subclause
15.3.2 item b.
Page 25
Replace “next synchronization Point serial number” with “next synchronization Point number”
in subclause 16.3.1 item c.
Replace “next synchronization Point serial number” with “next synchronization Point number”
in subclause 16.3.1 item g.
Replace “synch Point serial number” with “synchronization Point serial number” in subclause
16.3.2 item b.
“expected synchronization number”
Replace with “next synchronization Point number” in
subclause 17.2.5 item b.
Page 26
Replace “synchronization Point number” with “synchronization Point serial number” and
replace “next resynchronization Point serial number” with “next synchronization Point number”
in the last sentence of the Paragraph in subclause 17.3.1.
Replace “resynchronization Point number” with “synchronization Point serial number” in
subclause 17.3.3 item c.
“resynchronization Point number” with “synchronization Point serial number” in
Replace
subclause 17.3.4 item d.
Replace “resynchronization Point number” with “synchronization Point serial number” in
subclause 17.3.5 item e.
---------------------- Page: 6 ----------------------
ISO 857%4:1988/Amd.4:1992 (E)
Page 27
Replace “indication Permanent” with “indication. Permanent” in subclause 18.1.3 last
Paragraph.
Page 28
In subclause 19.1.1 item a replace “carrying” with “not carrying ”.
Add “d) issue an F-INITIALIZE request to the IFS provider.” to subclause 19.1.2.1.1.
Page 29
In subclause 19.1.4 Paragraph Change the word “when” to “while ”.
Replace “F-INITIALIZE request” with “F-INITIALIZE response” in subclause 19.1.5.3.
Replace “FERPM and shall retain” with “FERPM shall retain” in subclause 19.1.5.4.
Page 30
In subclause 19.2.1 first sentence Position the sentence after figure 4.
Replace subclause 19.2.1.3 with the following:
“lf the entity is a sending entity, the F-RESTART request shall include the last
acknowledged Point as a recovery Point.”
Replace “Write or Read procedure” with “Read or Write procedure” in figure 5.
Replace “’ it shall discard the primitive.” with “’ it shall decide that it is a collision-loser in the
Session layer and shall send an F-RESTART response as a response to the F-RESTART
in the last sentence sf subclause 19.2.1.7.
indication.” I
Page 37
In 19.2.3.4 c) replace the words:
“and an F-U-ABORT request to the internal file Service provider, with a diagnostic.”
by the words:
“and locally Signal the internal file Service provider to issue a F-P-ABORT PDU with a
diagnostic.”
Page 33
Add the following comments in the ASN.l (subclause 20.3):
Insert after lines 29 and 45 the following:
nal units are not available, the
“- If the recovery of restart data transfer functio
Checkpoint window Parameter shall not be sent.”
---------------------- Page: 7 ----------------------
ISO 857%4:1988/Amd.4:1992 (E)
Page 37
Insert after line 255 the following:
“- If the fadu-locking functional unit is not available, the enable-fadu-locking Parameter
shall not be sent.”
Change line 260 from “at-start-of-file” to “at-start-of-transfer ”.
Insert after line 275 the following:
“- If the recovery or restart data tran sfer functional unit are not available, the recovery-
mode Parameter sha II not be sent.”
Page 38 ’
Insert after lines 309 and 319 the following:
“--The recovery-Point Parameter shall only be sent by the entity that was receiving data
at the time of failure.”
Page 40
At least one attribute Parameter
Add an ASN.l note in subclause 20.3 after line 470 stating “-
shall be present in Change Attributes on the request PDU ”.
Page 43
Add a note after line 654 of figure 11:
“- in the case where the Parameter is a null list, “NULL” shall be
--
explicitly encoded.”
Page 45
Add a new subclause 20.5 titled “Rules of extensibility” with the following text:
“For the F-INITIALIZE request FPDU, a receiving Responder FPM shall:
a) ignore any undefined element;
b) where named bits are used in subclause 20.3, treat any as insignificant when
no name is assigned to it.
Pages 47 to 85
Replace annex A with the attached text.
The following subclauses have been amended:
A.l.l, A.1.2, A.l.6, A.1.7, A.2.4, A.2.7, A.2.9, A.3.4, A.3.5, A.3.9, A.4.4, A.4.6, A.4.7, A.4.8, A.4.9,
A.5.2.1, A.5.2.2, A.5.2.3, A.5.3.1, A.5.3.2, A.5.3.3, A.5.4, A.5.5, A.5.6, A.5.7, A.5.8, A.5.9, A.5.11,
A.5.12, A.5.13, A.5.15 and A.5.17.
---------------------- Page: 8 ----------------------
ISO 8571.4:1988/Amd.4:1992 (E)
Annex A
Protocol state tables
(This annex forms part of the Standard.)
users to be invalid at some Service interface.
A.1 Introduction
The conventions adopted in this Annex are described
below.
In the event of a discrepancy becoming apparent in the
protocol described in the bodv of this Standard and the
A.l .l System model used for protocol
protocol described in this Annex, this Annex is to take
description
precedence.
There are four types of receivers and sources of
These tables describe the Operation of the basic file
incoming and outgoing events (see figure 12):
protocol machine (FPM) and error recovery protocol
machine (FERPM).
a) The internal file Service User, which is the file
error recovery protocol machine (FERPM);
The basic protocol tables are divided into three groups,
covering:
b) The external file Service user - initiator or
responder;
a) the FTAM regime management protocol machine;
c) The local System environment;
b) the file regime management protocol machine;
d) the underlying presentation and ACSE Service
c) the bulk data transfer protocol machine.
providers.
The initial and final states of the file regime management
All primitives to/from the external file Service user are
protocol machine are also states of FTAM regime
passed through as primitives to/from the internal file
management protocol machine. The initial and final
Service user to the basic FPM.
states of the bulk data transfer protocol machine are
also states of the file regime management protocol
If the FERPM is not null - that is, either the RESTART
machine.
or the RECOVER functional unit is available -
Parameters needed for error control and recovery may
To provide formally complete and consistent description
be added to these primitives.
of the FTAM protocol sequences of events are
considered indivisible in the model. That indivisibility
Signals to/from the local environment group together
ensures both that the states used in the description are
events signalling errors and events signalling
weil defined and that they are sufficient to describe the
interactions amongst the FERPM, its decket and its
protocol.
local System. These local Signals are
The reception of a Service primitive and the generation
e) L-ERRABT - local Signal indicating protocol or
of dependent actions are considered to be an indivisible
other local errors leading to F-P-ABORT, with a
action. The reception of an FPDU and the generation of
permanent error value in the action result Parameter;
dependent actions are considered to be an indivisible
action.
f) L-PABORT - local Signal indicating that a F-P-
ABORT request PDU with a transient error value in the
The indivisibility of actions may, in some
action result should be issued;
implernentations, Cause certain events from file Service
to/from external
file Service user
File error recovery
I
protocol machine
(FERPM)
to/from internal
to/f rom local
file Service user
environment
(include FERPM)
Basic protocol machine
FPM
to/from presentation
or ACSE provider
Figure 12 - State machine System model
---------------------- Page: 9 ----------------------
ISO 8571-4:1988/Amd.4:1992 (E)
g) L-ERRORI, L-ERROR2 and L-ERROR3 - local The receipt of sequences of Service events are
Signals indicating class 1, class II and class Ill errors assumed to be permissible in accordance with those
respect ively; defined in ISO 8571-3.
h) L-SUSPND - a local Signal sent by the sender in Events in the tables are depicted by abbreviated
the RESTART state to the local System to suspend names. A list of these abbreviations, arranged
the issuing of F-DATA request and F-DATA-END alphabetically within categories, precedes each table.
request primitives; Wherever possible, these events have been arranged in
the Order in which a normal error-free sequence of
L-RESUME - a local Signal to the local System to
0
events would occur.
resume the issuing of F-DATA request and F-DATA-
END request primitives when a sender has completed lt is assumed that incoming PDUs have been extracted
its recovery from RESTART and is now back in DATA- from the user data fields of Presentation or ACSE
XFER state; indication or tonfirm primitives Prior to being considered
. as incoming events.
L-RESEND - a local Signal from the FERPM to
1)
the sending local System. This Signal includes the The following naming conventions are used:
negotiated restart Checkpoint and eliminates the need
a) The prefix “F-” (as in F-INIRQ) indicates a
to store data values in the decket. Upon receipt of
primitive issued by the external file Service (EFS) user
this local Signal the local System tan either
or issued by the FERPM to the EFS User;
‘1) resend data from the Checkpoint if the local
b) The prefix “P-” (as in P-ALTRQ) indicates a
System is aware of the algorithm used by the
primitive issued by the Presentation Service (PS)
FERPM to generate the Checkpoint; or
provider.
2) resend data from the Start of the file if it has no
c) The prefix “A-” (as in A-PABIN) indicates a
knowledge of the Checkpoint generating algorithm.
primitive issued by the ACSE provider;
The FERPM in the RESTART state will discard all
data from the local System that occurs before the
d) The prefix “L-” (as in L-ERRABT) indicates a local
negotiated Checkpoint. The FERPM will only
Signal from the FPM or the FERPM to the local System
forward data past the negotiated Checkpoint to the
or from the local System environment to the FPM or
FPM;
the FERPM;
k) L-DATRQ - Signal representing a re-issued F-
e) The prefix “I-” (as in 1-OPNRQ) indicates a
DATA request primitive from the local System;
primitive issued by the FERPM to the FPM or vice-
versa;
1) L-DAERQ - Signal representing a re-issued F-
DATA-END request primitive when a “data-end”
f) Where no prefix is used, the event is the receipt
marker becomes available from the decket;
of an FTAM PDU or, in the case of GRPRQ and
GRPRP, a grouped sequence of PDUs. The only
m) L-CHKRQ - Signal representing a re-issued F-
exception is “DATIN” which indicates a data value in
CHECK request primitive when a Checkpoint identifier
user context in the data transfer state.
becomes available from the decket;
g) The following suffices indicate the basic types of
n) L-EORIN - end of restart indication Signal
primitives and PDUs:
indicating that all Checkpoint identifiers, “data-end”
markers are all data to be resent have been sent;
“RQ” request
“1 N” indication
o) L-GIVEUP - Signal indicating that the
“RP”
response
responding FERPM should abandon the recovery
“CF’ conf irm
process. This is introduced so that if the initiating
FERPM is unable to re-establish the association then
A.1.3 Outgoing Events
the responding FERPM tan inform its users of the
irrecoverable error.
The same naming conventions are used for outgoing
events as for incoming events. Where the outgoing
p) L-ERRCTX - Signal indicating that the P-ALTER-
event is the issue of a PDU, it will normally give rise to
CONTEXT negotiation is unsuccessful. The error is to
the similarly named incoming event for the other
be processed following the F-OPEN or F-RECOVER
protocol entity. For example, the outgoing event SELRP
tonfirm as applicable.
of the responding entity will become the incoming event
q) L-HOLD - Signal to FERPM to hold any primitive
SELRP for the initiating entity.
from the external user for later processing.
A.1.4 States
r) L-UNHOLD - Signal to FERPM to process any
previously held primitives.
The suffix “-PD” indicates a pending state, waiting for
some known primitive or PDU type. The suffix “-EX’
--- a local Signal from the FERPM to
s) L-STPSND
indicates an expectant state in FERPM, waiting for
the sending local System to stop the resending of
some expected primitive.
data and Checkpoints.
The prefix “P-” normally indicates waiting for a primitive
A.1.2 Incoming Events
from the Presentation Service provider. Similarly, the
8
---------------------- Page: 10 ----------------------
ISO 857%4:1988/Amd.4:1992 (E)
prefix “F-” indicates waiting for a primitive from the EFS c) a specified qualifier, indicated by a number in
User. If neither of the above prefices is used, the state Square brackets [ ] following a preceding item without
normally indicates waiting for a PDU, or a non-pending a intervening comma;
state.
Actions are qualifiers are described in a Single list
preceding the table.
A.1.5 Predicates
The next state which the protocol entity will enter is
The following Symbols used in pre dicates have their
indicated by an arrow preceding a state name, e.g. ‘5
normal Boolean algebraic meanings:
SELECTED ”. For the null transition back to the current
& AND
state, the notation “3 same state” is used.
l OR
NOT Once a state Change occurs all subsequent actions in
9
that e nt ry are ignored
An incoming event may satisfy more than one predicate,
in which case the conditional actions for satisfied
A.l.7 Implicit Action
predicates will be executed.
The following entity actions have not been explicitly
Some actions may be conditional upon the neg otiatio n
specified in the State tables, but constitute patt of the
of particular Service fu nctional units;
entity behaviour:
those in the FPM are:
a) A blank Square in the table indicates an invalid
Ul: Kerne1 functional unit event.
u2: Read functional unit
b) Unless otherwise stated in the tables, an invalid
u3: Write functional unit
event would Cause the action specified in 10.2 to be
u4: File access functional unit
executed.
u5: Limited management functional unit
U6: Enhanced management functional unit
c) The Presentation Service is used throughout to
u7: Grouping functional unit
identify “active” FTAM PCI from data with an
U8: FADU locking functional unit
equivalent encoding, but in a “passive” use data
context.
those in the FERPM are:
d) For each incoming PDU, a check is made that the
u9: Recovery functional unit
appropriate functional unit has been negotiated for
UIO: Restart data transfe r funct ional unit
the connection. If the check fails, the procedures for
protocol Violation specified in 10.2 are followed.
A.1.6 Actions
e) For each incoming PDU the permissible
Actions may be conditional on specified predicates, or
sequences of Service events as defined in ISO 8571-
they may be unconditional. When a line in a “detailed
3 shall be checked. If the check fails the procedures
entries” specification commences with a predicate
for protocol Violation specified in 10.2 are followed.
specifier followed by a colon, this indicates that all
actions on that line are conditional upon the indicated
A.1.8
Additional State Information
predicate. An action may consist of one or more of the
following:
The tables make use of the indicators and other state
variables defined in 6.2 and 11.2. In addition, the file
a) an outgoing event, indicated by its abbreviated
regime management tables for the initiator make use of
name;
a threshold indicator and an expected response list, as
b) a specified action, indicated by a number in a means of specifying the entity state when a
Square brackets [ ] and separated from any preceding concatenated PDU group is outstanding.
items by a comma;
The Symbol NSPN is used to denote the Next
Synchronization Point Number state variable.
---------------------- Page: 11 ----------------------
ISO 857%4:1988/Amd.4:1992 (E)
FTAM regime management protocol machine (Kerne1 functional unit)
A.2
A.2.1 States - FTAM regime management
UNINITIALIZED FTAM regime ended.
lnitialize pending; wait for initialize response PDU.
INITIALIZE-PD
IN ITIALIZED FTAM regime started.
TERMINATE-PD Terminate pending; wait for terminate response PDU.
Initialize pending; wait for F-INITIALIZE response primitive from the internal file Service User.
1-INITIALIZE-PD
Terminate pending; wait for F-TERMINATE response primitive from the internal file Service
1-TERMINATE-PD
User.
Any other state of the file regime management protocol machine or the bulk data transfer
ANY-OTHER
protocol machine.
nagemen t
A.2.2 Incomin events - FTAM regime
g
th e functio nal unit in which the t occurs is included after the name, where ap
In the fol lowing lists,
A.2.2.1 Incoming events - PDUs
UABRQ U-Abort request PDU (on A-ABORT indication primitive) Ul
PABRQ P-Abort request PDU (on A-ABORT indication primitive)
INIRQ Initialize request PDU
INIRP Initialize response PDU
TERRQ Terminate request PDU
TERRP Terminate response PDU
A.2.2.2 Incoming events from the internal file Service user
1-UABRQ F-U-ABORT request primitive
1-INIRQ F-INITIALIZE request primitive
1-INIRP F-INITIALIZE response primitive
1-TERRQ F-TERMINATE request primitive
1-TERRP F-TERMINATE response primitive
A.2.2.3 Incoming events from the ACSE provider
A-PABIN A-P-ABORT indication primitive
A-ABIN A-ABORT indication primitive without user data
A-ASSCF A-ASSOCIATE tonfirm primitive without user data (with result indicating reject by ACSE or
presentation Service provider)
A.2.2.4 Incoming events from the local System
L-ERRABT Local Signal indicating error leading to abort
L-PABORT Local Signal indicating that a F-P-ABORT request PDU and a F-P-ABORT indication primitive to the
internal file Service User, both with a transient error value.
FTAM regime management
A.2.3 Outgoing events -
A.2.3.1 Outgoing events - PDUs
U-Abort request PDU
UABRQ
PABRQ P-Abort request PDU
10
---------------------- Page: 12 ----------------------
ISO 857%4:1988/Amd.4:1992 (E)
INIRQ Initialize request P@lJ
INIRP Initialize response PDU
TERRQ Terminate request PDU
TERRP Terminate response PDU
A.2.3.2 Outgoing events to the internal file Service user
1-UABIN F-U-ABORT indication primitive
1-PABIN F-P-ABORT indication primitive
1-INIIN F-INITIALIZE indication primitive
1-INICF F-INITIALIZE tonfirm primitive
1-TERIN F-TERMINATE indication primitive
1-TERCF F-TERMINATE tonfirm primitive
A.2.4 Specific actions - FTAM regime management
Send the PDU constructed as user data and map Parameters on the appropriate ACSE form.
[11
Initialize state information - unset all additional state information indicators, set outstanding Checkpoint
Pl
counter to Zero, NSPN to one.
Set state result Parameters to “success ”.
VI
In case of ACSE provider abort, if any diagnostic indicates communications failure then set the action result
Fl
to transient error.
Set state result Parameter to ‘failure ”.
Fl
Record the FQOS required and select the restart and/or recovery functional units if necessary.
VI
Establish the list of presentation contexts needed to support FTAM PCI and ACSE PCI abstract syntaxes.
Wl
If necessary, determine, on the basis of the abstract syntaxes derived from the contents type list supplied
by the external file Service User, the list of presentation contexts needed to support the file contents, and
add it to the previous list. The resultant list is used to construct the presentation context definition list
Parameter.
Update the value of the contents type list Parameter in the F-INITIALIZE indication primitive issued to the
Wl
internal file sen/ice User, according to the abstract syntaxes rejected by the presentation Service provider,
if necessary.
According to the value of the contents type list on the F-INITIALIZE response primitive received from the
Wl
internal file Service User, construct the presentation context definition result Parameter.
Set the action result Parameter according to the result Parameter of the A-ASSOCIATE tonfirm Service
PO1
primitive.
Record the peer entity ’s Checkpoint window.
Wl
Set action result to permanent error
PO1
Set action result to transient error
PU
A.2.5 Predicates - FTAM regime management
Pl: 1-INITIALIZE request primitive is acceptable.
P2: Result Parameter of the ACSE tonfirm primitive indicates success of the Operation.
P3: State result Parameter of the incoming response primitive indicates success of the Operation.
P5: Initialize request PDU is acceptable.
Negotiable Parameters have values consistent with request.
P25:
11
---------------------- Page: 13 ----------------------
ISO 857%4:1988/Amd.4:1992 (E
Initiating entity state tab
A.2.6 e- FTAM regime management
TATE ü -i-
N N T
I I I E
N T N R
I I I M A
T A T I N
I L I N Y
A I A A
L Z L T 0
I E I E T
Z Z H
E P E P E
VENT D D D D R
X W E C =
INITRQ 1
-ASSCF iö
JIRP -2
TERRQ 3
ERRP 4
-PABIN 5 -5 5- 5
-ABIN 7 7 7 7
ABRQ 6 6 6 6
ABRQ 7 7 7 7
JABRQ 8 8 8 8
*ERRABT 9 9 9 9
.PABORT ii- 11 Ti- ii
A.2.7 Initiating entity state table: detailed entries
1: Pl:
[3],[12],INIRQ[l] a INITIALIZE-PD
-Pl: 1-INICF[G] 3 Same state
2: P3&P2 & P25: [62],I-INICF[4],[7] * INITIALIZED
P3&P2 81 -P25: l-lNICF[G],PABRQ[l]
* UNINITIALIZED
-P2: 1-INICF[6]
3 UNINITIALIZED
-P3: PABRQ[l],l-PABIN[80]
a UNINITIALIZED
3: TERRQ[l]
* TERMINATE-PD
4: 1-TERCF
3 UNINITIALIZED
5: l-PABIN[81]
a UNINITIALIZED
6:
1-UABIN a UNINITIALIZED
7: 1-PABIN
a UNINITIALIZED
8: UABRQ[l] + UNINITIALIZED
9: PABRQ[l],l-PABIN[80] =a UNINITIALIZED
10: 1-lNlTCF[G],l-PABlN[20] 3 UNINITIALIZED
11: PABRQ[l],I-PABIN[81]
q UNINITIALIZED
12
---------------------- Page: 14 ----------------------
ISO 857%4:1988/Amd.4:1992 (E)
A.2.8 Responding entity state table - FTAM regime management
3TATE -T
I
U I
N N T
I I I E
N T N R
I I
I M A
T A T I N
I L l N Y
A I A
A
L Z L T 0
I E I E T
Z Z l-i
E P E e E
SVENT D D D D R
E E E E C
NIRQ 1
-INIRP 2
TERRQ 3
-TERRP 4
4-PABIN 5 5 5 5
4-ABIN 7 7 7 7
JABRQ 6 6 6 6
‘ABRQ 7
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.