Working Implementation Agreements for Open Systems Interconnection Protocols: Part 19 - Remote Database Access Output from the December 1993 OSE Implementors' Workshop (OIW) SIG Chair: Peter Eng, IBM Canada SIG Editor: Joel Berson, Santosh Hasani, Digital Equipment Corp. ii Part 19 - Remote Database Access December 1993 (Working) Foreword This part of the Working Implementation Agreements was prepared by the Remote Database Access Special Interest Group (RDA SIG) of the Open Systems Environment Implementors' Workshop (OIW). See Part 1 - Workshop Policies and Procedures in the "Draft Working Implementation Agreements Document" for the workshop charter. Text in this part has been approved by the Plenary of the Workshop. This part replaces the previously existing part on this subject. Future changes and additions to this version of these implementation Agreements will be published as change pages. Deleted and replaced text will be shown as strikeout. New and replacement text will be shown as shaded. iii Part 19 - Remote Database Access December 1993 (Working) iv Part 19 - Remote Database Access December 1993 (Working) Table of Contents v Part 19 - Remote Database Access December 1993 (Working) List of Tables vi Working Implementation Agreements for Open Systems Interconnection Protocols: Part 20 - Manufacturing Message Specification (MMS) Output from the December 1993 OSE Implementors' Workshop (OIW) SIG Chair: Rick Igou, Martin Marietta Energy Systems SIG Editor: Neal Laurance, Ford PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) Foreword This part of the Working Implementation Agreements was prepared by the Manufacturing Message Specification (MMS) Special Interest Group (MMSSIG) of the National Institute of Standards and Technology (NIST) Workshop for Implementors of Open Systems Interconnection (OSI). See Part 1 - Workshop Policies and Procedures in the "Draft Working Implementation Agreements Document" for the workshop charter. Text in this part has been approved by the Plenary of the above- mentioned Workshop. No significant technical change has occurred in this part since it was previously presented. Future changes and additions to this version of these Implementor Agreements will be published as a new part. Deleted and replaced text will be shown as strikeout. New and replacement text will be shown as shaded. ii PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) Table of Contents iii Part 20 - Manufacturing Message Specification (MMS) 0 Introduction (Refer to the Stable Agreements, Version 6.) 1 Scope (Refer to the Stable Agreements, Version 6.) 2 Field of Application 3 Normative References (Refer to the Stable Agreements, Version 6.) 4 Definitions (Refer to the Stable Agreements, Version 6.) 5 Corrigenda and Addenda ISO/IEC 9506-1:1993 - Industrial automation systems - Manufacturing Message Specification: Technical Corrigenda 1 6 Status Phase 1 is in progress. 7 General Agreements 7.1 Max supported PDU size (Refer to the Stable Agreements, Version 6.) 1 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) 7.2 FileName (Refer to the Stable Agreements, Version 6.) 7.3 Order of capabilities (Refer to the Stable Agreements, Version 6.) 7.4 Constructed Encodings Constructed encodings shall not be used for bit strings shorter than 256 bits, nor for octet strings (or types derived from octet strings by tagging) shorter than 1024 octets. For such strings, only primitive encodings shall be used. Upon receipt of a constructed bit string or octet string that violates this restriction, the receiving implementation may reject the corresponding PDU, but shall not send a P-P-Abort. 8 Service-Specific Agreements 8.1 Environment and general management 8.1.1 Initiate 8.1.1.1 Negotiation of MMS abstract syntaxes (Refer to the Stable Agreements, Version 6.) 8.1.1.2 Max serv outstanding (Refer to the Stable Agreements, Version 6.) 8.1.1.3 Local detail calling (Refer to the Stable Agreements, Version 6.) 8.1.1.4 Local detail called (Refer to the Stable Agreements, Version 6.) 2 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) 8.1.1.5 Rules of Extensibility (Refer to the Stable Agreements, Version 6.) 8.2 VMD Support (Refer to the Stable Agreements, Version 6.) 8.3 Domain Management 8.3.1 List of capabilities (Refer to the Stable Agreements, Version 6.) 8.3.2 Initiate Download Sequence service (Refer to the Stable Agreements, Version 6.) 8.3.3 Download Segment service (Refer to the Stable Agreements, Version 6.) 8.3.4 Terminate Download Sequence service (Refer to the Stable Agreements, Version 6.) 8.3.5 Initiate Upload Sequence service (Refer to the Stable Agreements, Version 6.) 8.3.6 Upload Segment service (Refer to the Stable Agreements, Version 6.) 8.3.7 Get Domain Attributes service (Refer to the Stable Agreements, Version 6.) 3 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) 8.4 Program Invocation Management 8.4.1 Start service (Refer to the Stable Agreements, Version 6.) 8.4.2 Stop service (Refer to the Stable Agreements, Version 6.) 8.4.3 Resume service (Refer to the Stable Agreements, Version 6.) 8.4.4 Reset service (Refer to the Stable Agreements, Version 6.) 8.5 Variable Access 8.5.1 Scattered access (Refer to the Stable Agreements, Version 6.) 8.5.2 Floating point (Refer to the Stable Agreements, Version 6.) 8.5.3 Unsigned Data (Refer to the Stable Agreements, Version 6.) 8.5.4 Order of variable specifications (Refer to the Stable Agreements, Version 6.) 4 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) 8.5.5 Parameter CBBs (Refer to the Stable Agreements, Version 6.) 8.5.6 Named Variable Scope (Refer to the Stable Agreements, Version 6.) 8.5.7 Address Types (Refer to the Stable Agreements, Version 6.) 8.6 Semaphore Management Semaphore services are not considered in Phase 1. 8.7 Operator Communication (Refer to the Stable Agreements, Version 6.) 8.8 Event Management Event Management services are not considered in Phase 1. 8.9 Journal Management Journal Management services are not considered in Phase 1. 5 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) Annex A (normative) Backwards compatibility agreements (Refer to the Stable Agreements, Version 6.) 6 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) Annex B (normative) DIS 9506 modifications required for backwards compatibility (Refer to the Stable Agreements, Version 6.) 7 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) Annex C (normative) Basic functional tests (Refer to the Stable Agreements, Version 6.) Table 43 - SQLSTATE values for RDA errors . . . . . . . . . . 7 8 Part 19 - Remote Database Access 0 Introduction Refer to the Stable Implementation Agreements. D Scope Refer to the Stable Implementation Agreements. E Status Refer to the Stable Implementation Agreements. F Normative references Refer to the Stable Implementation Agreements. G Definitions and abbreviations Refer to the Stable Implementation Agreements. H Structure of RDA standards Refer to the Stable Implementation Agreements. I SQL specialization I.1 Service parameter limits/agreements Refer to the Stable Implementation Agreements. I.2 Limits for common parameters Refer to the Stable Implementation Agreements. 1 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) I.3 Other limits and agreements Refer to the Stable Implementation Agreements. I.4 Profiles The names of RDA profiles are of the form "ARD-abcd". ("ARD" is reserved in ISO/IEC TR 10000-2 for Remote database Access.) a identifies the RDA specialization: 0 = SQL Specialization b identifies the capabilities for transaction management: 0 = transactions accessing data resources through a single remote open system (RDA Basic application-context). The type of transaction management provided is one-phase commitment. 1 = transactions spanning more than one open system (the RDA TP application-context). The type of transaction management provided is two-phase commitment. c identifies the functionality provided; that is, the set of functional units or other major elements of function mandated by the profile. This may differ among the various RDA Specializations. See below for the definition of this element for the SQL Specialization. d identifies the role: 0 = client role; that is, the ability to initiate RDA requests. 1 = server role; that is, the ability to respond to RDA requests. (An implementation that provides both roles must specify both profiles.) For the SQL Specialization, the following functionalities are defined: ARD-000d = Immediate execution: the capability to immediately execute SQL statements. (The significant function is the RDA Immediate Execution functional unit.) ARD-001d = Stored execution: the capability to store and later 2 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) execute SQL statements. (The significant function is the RDA Stored Execution functional unit.) ARD-002d = Status: the capability to perform status operations on other dialogues. (The significant function is the RDA Status functional unit together with support for the controlServiceDataRequested parameter of the R-Initialize service.) ARD-003d = Cancel: the capability to perform cancel operations on other dialogues. (The significant function is the RDA Cancel functional unit together with support for the controlServiceDataRequested parameter of the R-Initialize service.) Profiles for the RDA TP application-context will be defined at a later time. Refer to the Stable Implementation Agreements for the rules for and descriptions of the RDA profiles. 3 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) Annex A (normative) RDA SIG object identifiers Refer to the Stable Implementation Agreements. 4 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) Annex B (normative) Protocol Implementation Conformance Statement No text. 5 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) Annex C (informative) SQLSTATE values for RDA errors If passed on from the RDA service provider to an SQL Application in the RDA Client, errors returned by the SQL Server in RDA Error Responses are mapped into SQLSTATE values as specified in Table 43, SQLSTATE values for RDA errors. 6 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) Table 43 - SQLSTATE values for RDA errors SQLSTATE RDA Service Error Name VALUE HZ001 accessControlViolation HZ002 badRepetitionCount HZ003 commandHandleUnknown HZ004 controlAuthenticationFailure HZ005 controlServicesNotAllowed HZ006 dataResourceAlreadyOpen HZ007 dataResourceHandleNotSpecified HZ008 dataResourceHandleUnknown HZ009 dataResourceNameNotSpecified HZ010 dataResourceNotAvailable HZ011 dataResourceUnknown HZ012 dialogueIDUnknown HZ013 duplicateCommandHandle HZ014 duplicateDataResourceHandle HZ015 duplicateDialogueID HZ016 duplicateOperationID HZ017 invalidSequence HZ018 noDataResourceAvailable HZ019 operationAborted HZ020 operationCancelled HZ021 serviceNotNegotiated HZ022 transactionRolledBack HZ023 userAuthenticationFailure HZ024 hostIdentifierError HZ025 invalidSQLConformanceLevel HZ026 rDATransactionNotOpen 7 PART 20 - Manufacturing Message Specification (MMS) December 1993 (Working) HZ027 rDATransactionOpen HZ028 sQLAccessControlViolation HZ029 sQLDatabaseResourceAlreadyOpen HZ030 sQLDBLArgumentCountMismatch HZ031 sQLDBLArgumentTypeMismatch HZ032 sQLDBLNoCharSet HZ033 sQLDBLTransactionStatementNotAllo wed HZ034 sQLUsageModeViolation SQLSTATE ACSE Service Error Name VALUE HZ200 A-AssociateFailurePermanent HZ201 A-AssociateFailureTransient HZ202 A-ReleaseFailure HZ203 A-AbortFailureServiceUser HZ204 A-AbortFailureServiceProvider SQLSTATE TP Service Error Name VALUE HZ500 BeginDialogueRejectedUser HZ501 BeginDialogueRejectedProvider HZ502 UError HZ503 UAbortRollbackTrue HZ504 UAbortRollbackFalse HZ505 PAbortRollbackTrue HZ506 PAbortRollbackFalse HZ507 HeuristicMix HZ508 HeuristicHazard HZ509 Rollback 8