ISO/IEC 10026-2:1998
(Main)Information technology — Open Systems Interconnection — Distributed Transaction Processing — Part 2: OSI TP Service
Information technology — Open Systems Interconnection — Distributed Transaction Processing — Part 2: OSI TP Service
Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Traitement transactionnel réparti — Partie 2: Service OSI TP
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 10026-2
Third edition
1998-10-15
Information technology — Open Systems
Interconnection — Distributed Transaction
Processing —
Part 2:
OSI TP Service
Technologies de l'information — Interconnexion de systèmes ouverts
(OSI) — Traitement transactionnel réparti —
Partie 2: Service OSI TP
Reference number
B C
ISO/IEC 10026-2:1998(E)
---------------------- Page: 1 ----------------------
ISO/IEC 10026-2:1998(E)
............................................................................................................................................... Page
Contents
Foreword.v
Introduction. vi
1 Scope.1
2 Normative references .1
3 Definitions.1
4 Abbreviations.4
5 Conventions.4
5.1 Service conventions.4
5.2 Usage of the term transaction.5
5.3 Usage of italics for notations.5
6 Overview of the OSI TP Service.6
7 Service facilities.6
7.1 Functional unit descriptions .6
7.2 Services contained in functional units.9
7.3 Service for modelling data transfer.10
7.4 Structure of service descriptions.10
7.5 Effects of dialogue termination .11
8 Service primitives and their parameters .12
9 Data transfer.14
9.1 Overview of data transfer.14
9.2 Data transfer service, TP-DATA .14
10 The Dialogue functional unit .16
10.1 Overview of the Dialogue functional unit.16
10.2 Dialogue Establishment service, TP-BEGIN-DIALOGUE.16
10.3 Dialogue Termination service, TP-END-DIALOGUE.21
10.4 User Error Reporting service, TP-U-ERROR .23
10.5 User Abort service, TP-U-ABORT .25
10.6 Provider Abort service, TP-P-ABORT.28
11 The Shared Control functional unit .30
11.1 Overview of the Shared Control functional unit.30
12 The Polarized Control functional unit.30
12.1 Overview of the Polarized Control functional unit .30
12.2 Grant Control service, TP-GRANT-CONTROL .30
12.3 Request Control service, TP-REQUEST-CONTROL .31
© 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 microfilm, without permission in writing from the publisher.
ISO/IEC Copyright Office • Case postale 56 • CH-1211 Genève 20 • Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
©
ISO/IEC ISO/IEC 10026-2:1998(E)
13 The Handshake functional unit.33
13.1 Overview of the Handshake functional unit .33
13.2 Handshake service, TP-HANDSHAKE.33
13.3 Handshake and Grant Control service, TP-HANDSHAKE-AND-GRANT-CONTROL.35
14 The commitment-related functional units .36
14.1 Introduction .36
14.2 Summary .37
14.3 Overview of the Chained Transactions functional unit.43
14.4 Overview of the Unchained Transactions functional unit.43
14.5 Begin Transaction service, TP-BEGIN-TRANSACTION .43
14.6 Deferred End Dialogue service, TP-DEFERRED-END-DIALOGUE .45
14.7 Deferred Grant Control service, TP-DEFERRED-GRANT-CONTROL .47
14.8 TP-PREPARE request.48
14.9 TP-PREPARE indication.49
14.10 TP-READY indication.50
14.11 TP-COMMIT request .51
14.12 TP-COMMIT indication .53
14.13 TP-DONE request.54
14.14 TP-COMMIT-COMPLETE indication .56
14.15 TP-ROLLBACK request.56
14.16 TP-ROLLBACK indication.57
14.17 TP-ROLLBACK-COMPLETE indication.58
14.18 Heuristic Reporting service, TP-HEURISTIC-REPORT indication .59
14.19 TP-READ-ONLY request .60
14.20 TP-READ-ONLY indication.62
14.21 TP-EARLY-EXIT request.63
14.22 TP-EARLY-EXIT indication.64
14.23 TP-ONE-PHASE request.65
14.24 TP-ONE-PHASE indication.67
14.25 TP-UNKNOWN indication.68
14.26 TP-UNKNOWN-COMPLETE indication.68
14.27 TP-COMPLETION-REPORT indication.69
Annexes
A Service state table.71
A.1 Overview.71
A.2 Dialogue States .71
A.3 Variables.73
A.4 Actions.78
A.5 Node Crash .85
A.6 Keys.85
A.7 Blank Intersections .86
A.8 Node Contingency Table.86
A.9 Service State Table .87
B Summary of changes to the third edition.136
Tables
Table 1 - Functional units and their services .9
Table 2 - Service for modelling data transfer.10
Table 3 - OSI TP service primitives .13
Table 4 - TP-DATA primitives and parameters.14
Table 5 - TP-BEGIN-DIALOGUE primitives and their parameters .16
Table 6 - TP-END-DIALOGUE primitives and their parameter.21
Table 7 - TP-U-ERROR primitives.23
Table 8 - TP-U-ABORT primitives and their parameters .25
Table 9 - TP-P-ABORT indication and its parameters.28
Table 10 - TP-GRANT-CONTROL primitives .30
Table 11 - TP-REQUEST-CONTROL primitives .31
iii
---------------------- Page: 3 ----------------------
©
ISO/IEC 10026-2:1998(E) ISO/IEC
Table 12 - TP-HANDSHAKE primitives and their parameter.33
Table 13 - TP-HANDSHAKE-AND-GRANT-CONTROL primitives and their parameter .35
Table 14 - TP-BEGIN-TRANSACTION primitives and their parameter.43
Table 15 - TP-DEFERRED-END-DIALOGUE primitives .45
Table 16 - TP-DEFERRED-GRANT-CONTROL primitives .47
Table 17 - TP-PREPARE request and its parameter.48
Table 18 - TP-PREPARE indication and its parameter .50
Table 19 - TP-READY indication .51
Table 20 - TP-COMMIT request .51
Table 21 - TP-COMMIT indication .53
Table 22 - TP-DONE request and its parameters.54
Table 23 - TP-COMMIT-COMPLETE indication.56
Table 24 - TP-ROLLBACK request.57
Table 25 - TP-ROLLBACK indication and its parameters.57
Table 26 - TP-ROLLBACK-COMPLETE indication .59
Table 27 - TP-HEURISTIC-REPORT indication and parameter.59
Table 28 - TP-READ-ONLY request and its parameter.60
Table 29 - TP-READ-ONLY indication.62
Table 30 - TP-EARLY-EXIT request and its parameters.63
Table 31 - TP-EARLY-EXIT indication and its parameters.64
Table 32 - TP-ONE-PHASE request.65
Table 33 - TP-ONE-PHASE indication .67
Table 34 - TP-UNKNOWN indication.68
Table 35 - TP-UNKNOWN-COMPLETE indication.68
Table 36 - TP-COMPLETION-REPORT indication and its parameters.69
Figures
Figure 1 - Combination of functional units and resulting dialogue types .8
Figure 2 - Unconfirmed TP-BEGIN-DIALOGUE sequence of primitives .19
Figure 3 - Confirmed TP-BEGIN-DIALOGUE sequence of primitives .19
Figure 4 - Unconfirmed TP-END-DIALOGUE sequence of primitives.21
Figure 5 - Confirmed END-DIALOGUE sequence of primitives.22
Figure 6 - TP-U-ERROR sequence of primitives.23
Figure 7 - TP-U-ERROR as the negative confirmation to a handshake service.24
Figure 8 - TP-U-ABORT sequence of primitives.26
Figure 9 - TP-P-ABORT sequence of primitives.29
Figure 10 - TP-GRANT-CONTROL sequence of primitives .30
Figure 11 - TP-REQUEST-CONTROL sequence of primitives .32
Figure 12 - TP-HANDSHAKE sequence of primitives .33
Figure 13 - TP-HANDSHAKE-AND-GRANT-CONTROL sequence of primitives.35
Figure 14 - TP-BEGIN-TRANSACTION sequence of primitives .44
Figure 15 - TP-DEFERRED-END-DIALOGUE sequence of primitives .45
Figure 16 - TP-DEFERRED-GRANT-CONTROL sequence of primitives .47
iv
---------------------- Page: 4 ----------------------
©
ISO/IEC ISO/IEC 10026-2:1998(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 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 part 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.
International Standard ISO/IEC 10026-2 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 21, Open systems interconnection, data management and open
distributed processing.
This third edition cancels and replaces the second edition (ISO/IEC 10026-2:1996), which has been
technically revised.
This part of ISO/IEC 10026 is technically aligned with ITU-T Recommendation X.861, but is not published as
identical text.
ISO/IEC 10026 consists of the following parts, under the general title Information technology — Open
Systems Interconnection — Distributed Transaction Processing:
— Part 1: OSI TP Model
— Part 2: OSI TP Service
— Part 3: Protocol specification
— Part 4: Protocol Implementation Conformance Statement (PICS) proforma
— Part 5: Application context proforma and guidelines when using OSI TP
— Part 6: Unstructured Data Transfer
Annex A forms an integral part of this part of ISO/IEC 10026. Annex B is for information only.
v
---------------------- Page: 5 ----------------------
©
ISO/IEC 10026-2:1998(E) ISO/IEC
Introduction
ISO/IEC 10026 is one of a set of standards produced to facilitate the interconnection of computer systems. It
is related to other International Standards in the set as defined by the Reference Model for Open Systems
Interconnection (ISO/IEC 7498-1). The Reference Model subdivides the area of standardization for
interconnection into a series of layers of specification, each of manageable size.
The aim of Open Systems Interconnection is to allow, with a minimum of technical agreement outside the
interconnection standards, the interconnection of computer systems
a) from different manufacturers;
b) under different management;
c) of different levels of complexity; and
d) of different technologies.
ISO/IEC 10026 defines an OSI TP Model, an OSI TP Service and specifies an OSI TP Protocol available
within the Application Layer of the OSI Reference Model.
The OSI TP Service is an Application Layer service. It is concerned with information which can be related as
distributed transactions, which involve two or more open systems.
This part of ISO/IEC 10026 defines a basic OSI TP Service. It provides sufficient facilities to support
transaction processing, and establishes a framework for coordination across multiple TP resources in
separate open systems.
ISO/IEC 10026 does not specify the interface to local resources or access facilities that are provided within
the local system. However, future enhancement of the standard may deal with these issues.
vi
---------------------- Page: 6 ----------------------
©
INTERNATIONAL STANDARD ISO/IEC ISO/IEC 10026-2:1998(E)
Information technology — Open Systems
Interconnection — Distributed Transaction Processing —
Part 2:
OSI TP Service
1 Scope
This part of ISO/IEC 10026 defines in an abstract way the Distributed Transaction Processing Service within
the Application Layer in terms of:
a) the actions and events of the service primitives;
b) the parameter data associated with each service primitive's action and event; and
c) the relationship between, and the valid sequences of these actions and events.
It does not specify individual implementations or products, nor does it constrain the implementation of entities
or interfaces within a computer system.
2 Normative references
The following standards contain provisions which, through reference in this text, constitute provisions of this
part of ISO/IEC 10026. At the time of publication, the editions indicated were valid. All standards are subject
to revision, and parties to agreements based on this part of ISO/IEC 10026 are encouraged to investigate the
possibility of applying the most recent editions of the standards indicated below. Members of ISO and IEC
maintain registers of currently valid International Standards.
ISO/IEC 7498-1:1994, Information technology - Open Systems Interconnection - Basic Reference Model: The
Basic Model.
Information technology - Open Systems Interconnection - Basic Reference Model:
ISO/IEC 7498-3:1997,
Naming and addressing.
ISO/IEC 8649:1996, Information technology - Open Systems Interconnection - Service definition for the
Association Control Service Element.
ISO/IEC 10026-1:1998, Information technology - Open Systems Interconnection - Distributed Transaction
Processing - Part 1: OSI TP Model.
ISO/IEC 10026-3:1998, Information technology - Open Systems Interconnection - Distributed Transaction
Processing - Part 3: Protocol specification.
ISO/IEC 10731:1994, Information technology - Open Systems Interconnection - Basic Reference Model -
Conventions for the definition of OSI services.
3 Definitions
For the purposes of this part of ISO/IEC 10026, the definitions given in ISO/IEC 10026-1 and the following
definitions apply.
1
---------------------- Page: 7 ----------------------
©
ISO/IEC 10026-2:1998(E) ISO/IEC
3.1 dialogue establishment indication outstanding: A dialogue state in which a TP-BEGIN-DIALOGUE
indication with the Confirmation parameter set to "always" has been issued but has not yet been responded
to by a TP-BEGIN-DIALOGUE response.
3.2 dialogue establishment request outstanding: A dialogue state in which a TP-BEGIN-DIALOGUE
request with the Confirmation parameter set to "always" has been issued but has not yet been responded to
by a TP-BEGIN-DIALOGUE confirm.
: A dialogue state in which a TP-END-DIALOGUE
3.3 dialogue termination indication outstanding
user error request
indication with the Confirmation parameter set to "true" has been issued while there is no
outstanding
, but has not yet been responded to by a TP-END-DIALOGUE response, or by a TP-U-ERROR
request.
3.4 dialogue termination request outstanding: A dialogue state in which a TP-END-DIALOGUE request
with the Confirmation parameter set to "true" has been issued, but has not yet been responded to by a TP-
END-DIALOGUE confirm, or by a TP-U-ERROR indication.
3.5 exclusive branch: A transaction branch on which one of the following is true:
- the dialogue is with the superior, ready can be sent, and either:
- ready can not be received; or
- there is tree checking at the node;
- the dialogue is with a subordinate, ready can be sent, ready can not be received, and either:
- the Read-only functional unit is not selected and the Early-exit functional unit is not selected; or
- there is tree checking at the node; or
- the dialogue is with a subordinate and the coordination level is "one-phase commitment" and either:
- the Read-only functional unit is not selected and the Early-exit functional unit is not selected; or
- there is tree checking at the node;
and if the Unchained Transactions functional unit is selected, none of the following service primitives have
been issued during the current transaction: TP-READY indication, TP-READ-ONLY indication, TP-ONE-
PHASE indication, or TP-EARLY-EXIT indication.
3.6 handshake indication outstanding: A dialogue state in which one of the following service primitives:
- TP-HANDSHAKE indication;
- TP-HANDSHAKE-AND-GRANT-CONTROL indication;
has been issued while there is no user error request outstanding, but has not yet been responded to by one
of the following service primitives (respectively):
- TP-HANDSHAKE response;
- TP-HANDSHAKE-AND-GRANT-CONTROL response;
the dialogue is coordinated
or by a TP-U-ERROR request, or, if , by a TP-EARLY-EXIT request or a TP-
rollback-initiating service primitive
EARLY-EXIT indication or any .
3.7 handshake request outstanding: A dialogue state in which one of the following service primitives:
- TP-HANDSHAKE request;
- TP-HANDSHAKE-AND-GRANT-CONTROL request;
has been issued, but has not yet been responded to by one of the following service primitives (respectively):
- TP-HANDSHAKE confirm;
- TP-HANDSHAKE-AND-GRANT-CONTROL confirm;
or by a TP-U-ERROR indication, or, if the dialogue is coordinated, by a TP-EARLY-EXIT request or a TP-
EARLY-EXIT indication or any rollback-initiating service primitive.
superior can send ready
3.8 ready can be received (on a branch) if the branch is with a superior and on the
branch, or the branch is with a subordinate and subordinate can send ready on the branch.
2
---------------------- Page: 8 ----------------------
©
ISO/IEC ISO/IEC 10026-2:1998(E)
subordinate can send ready
3.9 ready can be sent (on a branch) if the branch is with the superior and on
superior can send ready
the branch or the branch is with a subordinate and on the branch.
3.10 rollback-initiating indication: An indication or confirm that triggers a rollback; it is one of the following
service primitives:
- TP-ROLLBACK indication;
- TP-U-ABORT indication with the Rollback parameter set to "true";
- TP-P-ABORT indication with the Rollback parameter set to "true";
- TP-BEGIN-DIALOGUE confirm with the Rollback parameter set to "true".
3.11 rollback-initiating request: A request that triggers a rollback; it is one of the following service
primitives:
- TP-ROLLBACK request;
- TP-U-ABORT request for a coordinated dialogue not issued during the termination phase of a transaction
and neither a TP-READ-ONLY indication nor a TP-EARLY-EXIT indication has been issued for the
dialogue.
: A service primitive that triggers a rollback; it may be either a
3.12 rollback-initiating service primitive
rollback-initiating request rollback-initiating indication
or a .
3.13 static one-phase exclusive branch: An exclusive branch on which the coordination level is “one-
phase commitment”.
NOTE - this is only defined for a branch to a subordinate.
3.14 subordinate dialogue: A dialogue with a subordinate.
3.15 subordinate can send ready (on a branch) if the branch is with a subordinate and the Commit
functional unit is selected and the Dynamic Commit functional unit is not selected, or the Dynamic Commit
functional unit is selected and the Subordinate-may-send-ready parameter of TP-BEGIN-DIALOGUE request
was set to "true".
3.16 subordinate subtree: A subtree of a subordinate.
3.17 superior can send ready (on a branch) if the branch is with the superior and the Dynamic Commit
functional unit is selected and the Superior-may-send-ready parameter of TP-BEGIN-DIALOGUE indication
was set to "true".
3.18 superior dialogue: The dialogue with the superior.
3.19 termination phase of a transaction; termination phase: The phase of a transaction between
initiation of commitment or rollback and the end of the transaction.
This phase is entered, for a given TPSUI, upon issuance of a transaction completion request or a TP-
EARLY-EXIT request or any rollback-initiat
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.