• Shopping Cart
    There are no items in your cart

BS ISO/IEC 9579-1:1993

Superseded

Superseded

A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.

View Superseded by

Information technology. Open systems interconnection. Remote database access Generic model, service and protocol

Available format(s)

Hardcopy , PDF

Superseded date

15-08-2001

Superseded by

BS ISO/IEC 9579:2000

Language(s)

English

Published date

15-04-1994

€416.02
Excluding VAT

Foreword
Introduction
Section 1: Introduction
1.1 Scope
1.2 Normative references
1.3 Definitions
1.3.1 Basic Reference Model
1.3.2 Reference Model - Naming and Addressing
1.3.3 Service conventions
1.3.4 Application Layer Structure
1.3.5 Connection Oriented Presentation Service
         Definition
1.3.6 Service Definition for the Association Control
         Service Element
1.3.7 Specification of Abstract Syntax Notation One
         (ASN.1)
1.3.8 Commitment, Concurrency and Recovery
1.3.9 Distributed Transaction Processing
1.3.10 Reference Model of Data Management
1.3.11 Remote Database Access
1.3.11.1 database language
1.3.11.2 database language command
1.3.11.3 database language statement
1.3.11.4 database server
1.3.11.5 data resource
1.3.11.6 RDA client
1.3.11.7 RDA Control service
1.3.11.8 RDA dialogue
1.3.11.9 RDA dialogue-state model
1.3.11.10 RDA Generic Standard
1.3.11.11 RDA operation
1.3.11.12 RDA protocol machine
1.3.11.13 RDA server
1.3.11.14 RDA Service
1.3.11.15 RDA Specialization Standard, RDA Specialization
1.3.11.16 RDA transaction
1.4 Abbreviations
1.5 Conventions
1.5.1 Service conventions
1.5.2 Service parameter description
Section 2: Model
2.1 Concepts
2.1.1 Overview of the components
2.1.2 Database server concepts
2.1.2.1 Organization of data
2.1.2.2 RDA transactions
2.1.2.3 RDA operations
2.1.2.4 Database language commands
2.1.3 Communication concepts
2.1.3.1 RDA dialogues
2.1.3.2 Failure and recovery
2.1.4 RDA application-contexts
2.1.5 RDA Specialization Standards
Section 3: Service
3.1 Services
3.1.1 RDA Dialogue Management services
3.1.1.1 RDA Dialogue Initialization functional unit
3.1.1.2 RDA Dialogue Termination functional unit
3.1.2 RDA Transaction Management services
3.1.2.1 RDA Transaction Management functional unit
3.1.3 RDA Control services
3.1.3.1 Cancel functional unit
3.1.3.2 Status functional unit
3.1.4 Resource Handling services
3.1.4.1 Resource Handling functional unit
3.1.5 Database Language services
3.1.5.1 Immediate Execution DBL functional unit
3.1.5.2 Stored Execution DBL functional unit
3.2 Sequencing rules
3.2.1 RDA client sequencing rules
3.2.2 RDA server sequencing rules
Section 4: Protocol
4.1 Server execution rules
4.1.1 RDA dialogue-state model
4.1.1.1 RDA operation entity
4.1.1.2 RDA dialogue entity
4.1.1.3 Opened data resource entity
4.1.1.4 Defined DBL entity
4.1.2 General server execution rules
4.1.2.1 Generation of the RDA operation entity
4.1.2.2 Implementor defined errors
4.1.2.3 Beginning of an RDA operation
4.1.2.4 Cancellation of an RDA operation
4.1.2.5 Execution of an RDA operation
4.1.2.6 End of an RDA operation
4.1.2.7 Response to an RDA operation
4.1.2.8 Failure of the RDA dialogue
4.1.3 RDA Dialogue Management services
4.1.3.1 RDA Dialogue Initialization functional unit
4.1.3.2 RDA Dialogue Termination functional unit
4.1.4 RDA Transaction Management services
4.1.4.1 RDA Transaction Management functional unit
4.1.5 RDA Control services
4.1.5.1 Cancel functional unit
4.1.5.2 Status functional unit
4.1.6 Resource Handling services
4.1.6.1 Resource Handling functional unit
4.1.7 Database Language services
4.1.7.1 Immediate Execution DBL functional unit
4.1.7.2 Stored Execution DBL functional unit
4.2 RDA protocol machine
4.2.1 Functional units
4.2.2 Correspondence between RDA service primitives
         and RDA APDUs
4.2.3 Concatenation
4.2.4 State tables
4.2.4.1 Conventions
4.2.4.2 Actions to be taken by the RDAPM
4.2.4.3 States
4.2.4.4 Incoming events
4.2.4.5 Outgoing actions
4.2.4.6 Predicates
4.2.4.7 RDAPM state tables
4.2.5 Protocol procedures
4.2.5.1 Initialization of an RDA dialogue
4.2.5.2 Termination of an RDA dialogue
4.2.5.3 Initiation of an RDA transaction
4.2.5.4 Termination of an RDA transaction
4.3 Application-protocol-data-units
4.4 Conformance
4.4.1 Static conformance
4.4.2 Dynamic conformance
Section 5: Application-contexts
5.1 RDA Basic application-context
5.1.1 Application-context name
5.1.2 Purpose and scope
5.1.2.1 General description
5.1.2.2 RDA dialogue failure
5.1.3 Set of ASEs
5.1.4 SACF rules
5.1.4.1 Association establishment and release
5.1.4.2 RDA dialogue initialization and termination
5.1.4.3 Mapping rules
5.1.5 State transition diagrams
5.1.6 Use of optional features
5.1.6.1 A-ASSOCIATE
5.1.6.2 A-RELEASE
5.1.6.3 A-ABORT
5.1.6.4 A-P-ABORT
5.1.7 Conformance
5.1.7.1 Static conformance
5.1.7.2 Dynamic conformance
5.2 RDA TP application-context
5.2.1 Application-context name
5.2.2 Purpose and scope
5.2.3 Set of ASEs
5.2.4 SACF rules
5.2.4.1 Sequencing rules
5.2.4.2 Mapping rules
5.2.4.3 Concatenation rules
5.2.4.4 Transaction states
5.2.5 State transition diagrams
5.2.6 Use of optional features
5.2.6.1 A-ASSOCIATE
5.2.7 Conformance
5.2.7.1 Static conformance
5.2.7.2 Dynamic conformance
Section 6: Specializations
6.1 RDA Specialization Standards
6.1.1 General
6.1.2 Model
6.1.3 Service
6.1.4 Protocol
6.1.4.1 Server execution rules
6.1.4.2 State tables
6.1.4.3 Structure of RDA Specialization APDUs
6.1.4.4 Conformance
6.1.5 Application-contexts
Annex A: Relationship to the Application Layer structure
A.1 Introduction
A.2 RDA as an application-service-element
A.3 RDA application-contexts
A.4 RDA service-provider
Index

Specifies the OSI Remote Database Access (RDA) Service in terms of: the behaviour, as perceived from the OSI environment, of a database server; the behaviour, as perceived from the OSI environment, of an RDA client. The former is an application process that provides database storage facilities and database processing services; the latter is an application process that accesses remote database facilities. Includes definitions and abbreviations.

Committee
ICT/1
DevelopmentNote
DRAFT FOR COMMENT 91/67852 DC
DocumentType
Standard
Pages
170
PublisherName
British Standards Institution
Status
Superseded
SupersededBy
Supersedes

ISO 8650:1988 Information processing systems — Open Systems Interconnection — Protocol specification for the Association Control Service Element
ISO/IEC 10026-2:1998 Information technology Open Systems Interconnection Distributed Transaction Processing Part 2: OSI TP Service
ISO/IEC 7498-3:1997 Information technology — Open Systems Interconnection — Basic Reference Model: Naming and addressing
ISO 8823:1988 Information processing systems — Open Systems Interconnection — Connection oriented presentation protocol specification
ISO/IEC 9804:1998 Information technology Open Systems Interconnection Service definition for the Commitment, Concurrency and Recovery service element
ISO/IEC 9545:1994 Information technology Open Systems Interconnection Application Layer structure
ISO/IEC 8824:1990 Information technology — Open Systems Interconnection — Specification of Abstract Syntax Notation One (ASN.1)
ISO/IEC 10026-3:1998 Information technology Open Systems Interconnection Distributed Transaction Processing Part 3: Protocol specification
ISO/IEC 8649:1996 Information technology Open Systems Interconnection Service definition for the Association Control Service Element
ISO/IEC 8822:1994 Information technology Open Systems Interconnection Presentation service definition
ISO/IEC 10026-1:1998 Information technology Open Systems Interconnection Distributed Transaction Processing Part 1: OSI TP Model
ISO 8327:1987 Information processing systems — Open Systems Interconnection — Basic connection oriented session protocol specification

Access your standards online with a subscription

Features

  • Simple online access to standards, technical information and regulations.

  • Critical updates of standards and customisable alerts and notifications.

  • Multi-user online standards collection: secure, flexible and cost effective.