ISO/IEC 10026-3:1998
(Main)Information technology — Open Systems Interconnection — Distributed Transaction Processing — Part 3: Protocol specification
Information technology — Open Systems Interconnection — Distributed Transaction Processing — Part 3: Protocol specification
This part of ISO/IEC 10026 provides a) a statement (clauses 6 to 11) of the nature of the automaton giving the necessary behaviour of each of the participating entities which are providing the OSI TP Service, covering 1) the actions to be taken on receiving request and response primitives issued by a TP Service user invocation; 2) the actions to be taken on receiving indication and confirm primitives issued by the presentation service-provider; 3) the actions to be taken as a result of certain events within the local system; 4) the actions to be taken as a result of interactions with other ASEs; b) the definition (clause 12) of the abstract syntax required to convey the TP protocol control information; c) the conformance requirements to be met by implementations of this protocol (clause 13). The scope of this part of ISO/IEC 10026 is limited to the interconnection of systems; it does not specify or restrict the implementation of possible interfaces within a computer system.
Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Traitement transactionnel réparti — Partie 3: Spécification du protocole
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 10026-3
Third edition
1998-12-15
Information technology — Open Systems
Interconnection — Distributed Transaction
Processing —
Part 3:
Protocol specification
Technologies de l'information — Interconnexion de systèmes ouverts
(OSI) — Traitement transactionnel réparti —
Partie 3: Spécification du protocole
Reference number
B C
ISO/IEC 10026-3 : 1998 (E)
Contents. Page
Foreword . xi
Introduction. xii
1 Scope.1
2 Normative references .1
3 Definitions.2
4 Abbreviations.3
5 Conventions.3
6 Model of the PM.3
6.1 Overview.3
6.1.1 Principles of association usage.4
6.1.2 Functional unit capabilities and selection.4
6.1.3 Dialogue establishment.5
6.1.4 Soliciting dialogue establishment .6
6.1.5 Channel management.6
6.1.6 Channel utilization.7
6.1.7 Token control .7
6.1.8 Collisions of Ready Signals.8
6.1.9 Concatenation/separation .8
6.1.10 Embedding .9
6.2 OSI TP Protocol structure.9
6.2.1 Components of the PM .9
7 Execution Rules.12
7.1 Operation of the PM.12
7.1.1 Relationship of SAO(s) to MACF(s) .12
7.1.2 Input events to the PM .12
7.1.3 Action sequences.12
7.1.4 SACF queuing.13
7.1.5 Input event blocking at the PSAP.13
7.1.6 PM error conditions .14
7.2 Procedure rules.14
7.3 Definitions .16
7.4 Log records used by the PM.27
7.4.1 Log-ready record.27
7.4.2 Log-commit record .27
7.4.3 Log-heuristic record .27
7.4.4 Log-damage record.28
7.5 Recovery-context-handle.28
8 Use of ACSE, CCR and the Presentation Layer .28
8.1 Introduction .28
© ISO/IEC 1998
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or
utilized in any form or by any means, electronic or mechanical, including photocopying and micro-
film, without permission in writing from the publisher.
ISO/IEC Copyright Office • Case postale 56 • CH-1211 Genève 20 • Switzerland
Printed in Switzerland
ii
©
ISO/IEC ISO/IEC 10026-3 : 1998 (E)
8.2 Use of ACSE Service primitives.28
8.2.1 Use of the A-ASSOCIATE parameters .29
8.2.2 Use of the A-RELEASE parameters .29
8.2.3 Use of the A-ABORT and A-P-ABORT parameters.30
8.3 Use of CCR Service primitives.30
8.4 Use of the Presentation Layer .32
8.4.1 Use of Presentation Service primitives .32
8.4.2 Mapping of C-ROLLBACK-RI to Presentation .32
8.5 Association Management.32
8.5.1 Introduction.32
8.5.2 Association/dialogue compatibility.33
8.5.3 Association/channel compatibility.33
8.5.4 Initiating an association establishment.34
8.5.5 Receiving an association establishment indication .35
8.5.6 Responding to association establishment.36
8.5.7 Receiving confirmation of association establishment.37
8.5.8 Initiating an association release .38
8.5.9 Aborting an association.38
8.5.10 Initiating a dialogue solicitation.38
8.5.11 Responding to a dialogue solicitation.38
8.5.12 Receiving a rejection of a dialogue solictation .39
8.5.13 Successful dialogue solicitation.39
9 TP-ASE description .39
9.1 Introduction .39
9.2 AF Service Definition .40
9.2.1 AF-BEGIN-DIALOGUE .40
9.2.2 AF-BID.41
9.2.3 AF-END-DIALOGUE .41
9.2.4 AF-U-ERROR.41
9.2.5 AF-ABORT .41
9.2.6 AF-GRANT-CONTROL.41
9.2.7 AF-REQUEST-CONTROL .41
9.2.8 AF-HANDSHAKE .41
9.2.9 AF-HANDSHAKE-AND-GRANT-CONTROL.42
9.2.10 AF-DEFER .42
9.2.11 AF-BEGIN-TRANSACTION .42
9.2.12 AF-PREPARE .42
9.2.13 AF-REPORT .42
9.2.14 AF-ABORT-AND-REPORT.42
9.2.15 AF-NOCHANGE.43
9.2.16 AF-EARLY-EXIT.43
9.2.17 AF-RECOVER.43
9.2.18 AF-TOKEN-GIVE .43
9.2.19 AF-TOKEN-PLEASE.43
9.2.20 AF-SOLICIT-DIALOGUE.43
9.3 AF-Services and TP APDUs: parameters and field Mappings.43
9.3.1 AF-BEGIN-DIALOGUE request/indication/response/confirm, TP-BEGIN-
DIALOGUE-RI/-RC APDU.43
9.3.2 AF-BID request/indication/response/ confirm, TP-BID-RI/-RC APDU.46
9.3.3 AF-END-DIALOGUE request/ indication/response/confirm, TP-END-DIALOGUE-
RI/-RC APDU .47
9.3.4 AF-U-ERROR request/indication/response/confirm, TP-U-ERROR-RI/-RC APDU.47
9.3.5 AF-ABORT request/indication, TP-ABORT-RI APDU.48
9.3.6 AF-GRANT-CONTROL request/ indication, TP-GRANT-CONTROL-RI APDU.49
9.3.7 AF-REQUEST-CONTROL request/ indication, TP-REQUEST-CONTROL-RI
APDU.49
9.3.8 AF-HANDSHAKE request/indication/ response/confirm, TP-HANDSHAKE-RI/-RC
APDU.49
iii
©
ISO/IEC 10026-3 : 1998 (E) ISO/IEC
9.3.9 AF-HANDSHAKE-AND-GRANT-CONTROL request/indication/response confirm,
TP-HANDSHAKE-AND-GRANT-CONTROL-RI/-RC APDU .49
9.3.10 AF-BEGIN-TRANSACTION request/indication, TP-BEGIN-TRANSACTION-RI
APDU .49
9.3.11 AF-DEFER request/indication, TP-DEFER-RI APDU .50
9.3.12 AF-PREPARE request/indication, TP-PREPARE-RI APDU .50
9.3.13 AF-REPORT request/ indication, TP-REPORT-RI APDU.50
9.3.14 AF-ABORT-AND-REPORT request/indication.52
9.3.15 AF-NOCHANGE request/indication, TP-NEXT-TID-RI APDU .53
9.3.16 AF-EARLY-EXIT request/indication/ response/confirm, TP-EARLY-EXIT-RI/-RC
APDU .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.