BS ISO/IEC 11587:1996

1 Scope
2 Normative references
    2.1 Identical Recommendations/International
          Standards
    2.2 Paired Recommendation/International Standards
          equivalent in technical content
    2.3 Additional references
3 Abbreviations
4 Application context name
5 Component ASEs and ASOs
    5.1 ACSE
    5.2 ROSE
    5.3 CMISE
    5.4 SMASE
    5.5 TPASE
    5.6 CCR
6 Persistent application context rules
7 Control function (SACF/MACS) rules
    7.1 Objectives/summary
    7.2 Temporal ordering rules
    7.3 Concatenation rules
    7.4 References to base standard rules
    7.5 Other rules
8 Optional features
9 Error handling
10 Conformance
Annex A - Commentaries
Annex B - Scenarios
      B.1 Example use of Handshake and Shared Control
          functional units
      B.2 Example use of Commit functional unit for
          provider-supported transactions
      B.3 Another example use of Commit functional unit
          for provider-supported transactions

Gives a basie Systems Management context with TP and could be part of a family of contexts as additional requirements are defined for systems management.

The application context, defined in this Recommendation | International Standard, is available for an association in the systems management environment. The application context provides a basic Systems Management context with TP and may be part of a family of contexts as additional requirements are defined for systems management.

The application context, defined in this Recommendation | International Standard, satisfies the following requirements:

• support for grouping CMIS requests so that consistency constraints can be satisfied by coordinated changes that, if done individually, would not satisfy the constraints, without requiring provisions for rollback or recovery; and

• support for atomic synchronization of a set of CMIS requests with provisions for commitment, rollback, and recovery so that either all the CMIS requests are satisfactorily performed or none are performed.