BS ISO/IEC 9804:1998

Foreword
Introduction
1 Scope
2 Normative references
3 Definitions
3.1 Reference model definitions
3.2 Naming and addressing definition
3.3 Service conventions definitions
3.4 Presentation service definitions
3.5 ACSE service definitions
3.6 Application Layer structure definitions
3.7 CCR service definitions
4 Abbreviations
5 Conventions
6 Concepts
6.1 Use of CCR in a distributed application
        environment
6.2 CCR facilities
6.3 Heuristic decisions
7 Service definition
7.1 C-BEGIN service
7.2 C-PREPARE service
7.3 C-READY service
7.4 C-COMMIT service
7.5 C-ROLLBACK service
7.6 C-RECOVER service
8 Sequencing information
8.1 General
8.2 Events
8.3 States
8.4 Interpretation of the state table
8.5 Completing the branch
8.6 Collisions and disruptive services
9 Using CCR
9.1 General
9.2 Use of the CCR by a cooperating main service
9.3 Use of resynchronization
9.4 Use of transport expedited service
9.5 Starting a branch
Annexes
A CCR service-user rules
A.1 Introduction
A.1.1 Rule categories
A.1.2 Heuristic decision considerations
A.2 Compliance
A.3 CCR service primitive usage rules
A.3.1 C-BEGIN request primitive
A.3.2 C-PREPARE request primitive
A.3.3 C-READY request primitive
A.3.4 C-COMMIT request primitive
A.3.5 C-COMMIT response primitive
A.3.6 C-ROLLBACK request primitive
A.3.7 C-ROLLBACK indication primitive
A.3.8 C-RECOVER(ready) request primitive
A.3.9 C-RECOVER(commit) request primitive
A.3.10 C-RECOVER(done) response primitive
A.4 Atomic action data manipulation rules
A.4.1 Recording atomic action data that indicates an
        offer of commitment
A.4.2 Forgetting atomic action data that indicates an
        offer of commitment
A.4.3 Recording atomic action data indicating an order
        of commitment
A.4.4 Forgetting atomic action data indicating an
        order of commitment
A.5 Bound data manipulation rules
A.5.1 Changing bound data to produce the final state
A.5.2 Releasing bound data in the initial state as a
        part of rollback
A.5.3 Releasing bound data in the final state as part
        of commitment
A.5.4 Releasing bound data as part of a heuristic
        decision
A.6 CCR service-user data transfer rules
A.6.1 Data transfer request and response primitive
A.6.2 Data transfer indication and confirm primitive
B Relationship of CCR to the Application Layer
        Structure
B.1 CCR service-provider
B.2 CCR service-user
B.3 Atomic action tree
C CCR tutorial
C.1 Introduction
C.1.1 What is CCR?
C.1.2 Atomic action
C.1.3 Purpose
C.1.4 Using CCR
C.2 Structure of an atomic action tree
C.2.1 Model
C.2.2 CCR service-user
C.2.3 Branch and its identifiers
C.2.4 An example using JTM
C.3 CCR service-user information resources
C.3.1 Bound data
C.3.2 Atomic action data
C.3.3 Operational data
C.4 Concurrency
C.4.1 General considerations
C.4.2 Concurrency example - locking
C.5 Recovery
C.5.1 Atomic action data
C.5.2 Presumed rollback
C.5.3 AP and AE invocation identifiers
C.6 Time relations and sequence of service
        primitives
C.7 Comments on implementation complexity
C.8 Using the User Data parameter on CCR services
C.8.1 Level of commitment
C.8.2 CCR diagnostics
C.8.3 Application-semantics
C.8.4 Heuristic warning
C.9 Optional use of C-PREPARE
C.9.1 Implicit prepare semantic
C.9.2 Implicit conditional prepare and continue
C.9.3 C-READY and application-semantics collision
C.10 Use of session synchronize and resynchronize
        services

Defines services that are used on a single association to coordinate two application-entity invocations involved in an atomic action. Coverage includes: abbreviations, conventions, concepts, service definition, and sequencing information. Also gives detailed annexes.

This Recommendation | International Standard is intended for reference by other specifications when the functionality of commitment, concurrency and recovery is required. It can be referenced whenever the processing of two or more application-entity invocations in a distributed application needs to be organized into an atomic action.

This Recommendation | International Standard defines services that are used on a single association to coordinate two application-entity invocations involved in an atomic action. The determination of which application-entity invocations are involved in an atomic action is not within the scope of this Recommendation | International Standard.

This Recommendation | International Standard establishes the general principles for the coordinated use of the CCR services when more than two application-entity invocations are involved in a single atomic action, or when recovery is required after failure. The coordination of multiple associations and the related application-entity invocations that constitute an atomic action is achieved by a referencing specification in conjunction with this Recommendation | International Standard.

This Recommendation | International Standard is only applicable to a distributed application whose specification references this Recommendation | International Standard.

This Recommendation | International Standard does not specify individual implementations or products. It does not constrain the implementation of entities and interfaces within a computer system.

No requirement is made for conformance to this Recommendation | International Standard.

This Recommendation | International Standard includes requirements for compliance that apply to a referencing specification.

The CCR service defined in this Recommendation | International Standard requires that CCR Protocol Version 2 (or a later version) is being used.