ISO/IEC 9579-2:1998

Information technology - Open Systems Interconnection - Remote Database Access - Part 2: SQL Specialization

Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Accès aux bases de données à distance — Partie 2: Spécialisation SQL

General Information

• Status: Withdrawn
• Publication Date: 18-Feb-1998
• Withdrawal Date: 18-Feb-1998
• ICS: 35.100.70 - Application layer
• Technical Committee: ISO/IEC JTC 1/SC 32 - Data management and interchange
• Drafting Committee: ISO/IEC JTC 1/SC 32 - Data management and interchange
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 10-Jun-1999
• Completion Date: 30-Oct-2025

Relations

• Consolidated By: ISO 10644:2009 - Screw and washer assemblies made of steel with plain washers - Washer hardness classes 200 HV and 300 HV
• Effective Date: 06-Jun-2022
• Revises: ISO/IEC 9579-2:1993/Cor 1:1995 - Information technology - Open Systems Interconnection - Remote Database Access - Part 2: SQL specialization - Technical Corrigendum 1
• Effective Date: 15-Apr-2008
• Revises: ISO/IEC 9579-2:1993 - Information technology - Open Systems Interconnection - Remote Database Access - Part 2: SQL specialization
• Effective Date: 15-Apr-2008
• Revised: ISO/IEC 9579:1999 - Information technology - Remote Database Access for SQL
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTERNATIONAL ISOAEC
STANDARD 9579-2
Second edition
1998-02-l 5
Information technology - Open Systems
Interconnection - Remote Database
Access -
Part 2:
SQL Specialization
Technologies de I’informa tion - lnterconnexion de syst&mes owe&
(03) -AC&S aux bases de donnkes 2 distance -
Partie 2: Spkialisation SQL
ISO/IEC 9579-2: 1998(E)
Contents
. . . . . . . . . .I.
1 . GENERAL
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.
1.2 Normative references
1.3 Compatibility .
..................................................................................................
1.3.1 SQL Standards Supported
1.3.2 Upward Compatibility .
................................................................................................................................
1.4 Definitions
.............................................
1.4.1 Terms defined in ISO/IEC 9075 (Database Language SQL)
. . . . . .D.
1.4.2 Terms defined in this part of ISO/IEC 9579
1.4.2.1 SQL database resource .
......................................................................................................
1.4.2.2 RDA SQL statement
15 . Abbreviations .
..............................................................................................................................
16 . Conventions
2 . MODEL .
..........................................................................
. The RDA SQL Specialization Service mode1
/
3 6
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A. 1.1 Mapping to the general mode1 of the RDA Service
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Mapping to the Concepts of Database Language SQL
. . . . . . . . . . . . . . . .*.
3 . SERVICE
.....................................................................................
3.1 The RDA SQL Specialization Service
................................................................................
3.1.1 RDA Dialogue Management services
3.1.1.1 RDA Dialogue Initialization functional unit .
.................................................................................................
3.1.1.1.1 R-Initialize Service
.................................................................
3.1.1.2 RDA Dialogue Termination functional unit
...............................................................................................
3.1.1.2.1 R-Terminate Service
............................................................................
3.1.2 RDA Transaction Management services
............................................................
3.1.2.1 RDA Transaction Management functional unit
...................................................................................
3.1.2.1.1 R-BeginTransaction Service
..................................................................................................
3.1.2.1.2 R-Commit Service
.................................................................................................
3.1.2.1.3 R-Rollback Service
........................................................................................................
3.1.3 RDA Control Services
3.1.3.1 Cancel functional unit .
3.1.3.1.1 R-Cancel Service .
3.1.3.2 Status functional unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .*.
3.1.3.2.1 R-Status Service
...............................................................................................
3.1.4 Resource Handling services
3.1.4.1 Resource Handling functional unit .
.......................................................................................................
3.1.4.1.1 R-Open Service
3.1.4.1.2 R-Close Service .
..............................................................................................
3.1.5 Database Language Services
3.1.5.1 Immediate Execution DBL functional unit .
...........................................................................................
3.1.5.1.1 R-ExecuteDBL Service
..........................................................................
3.1.5.2 Stored Execution DBL functional unit
3.1.5.2.1 R-DefineDBL Service .
0 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 l Case postale 56 l CH-1211 Geneve 20 l Switzerland
Printed in Switzerland
ii
ISO/IEC 9579-2: 1998(E)
0 ISO/IEC
3.1.5.2.2 R-InvokeDBL Service .
3.1.5.2.3 R-DropDBLService* . .
. .
3.1.6 SQL statements, arguments and results
3.1.6.1 sQLDBLStatement* . .
............................. 18
3.1.6.2 sQLDBLArgumentSpecification and sQLDBLResultSpecification
................................................. 23
3.1.6.3 sQLDBLArgumentValues and sQLDBLResultValues
.............................................................................................
3.1.6.4 Referencing to parameters
3.2 Sequencing rules .
.........................................................................................
3.2.1.1 RDA client sequencing rules
3.2.2 RDA Server Sequencing Rules .
4 . PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 The RDA SQL Specialization client execution rules
4.1.1 RDA SQL Specialization dialogue-state model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.
4.1.1.1 SQL Transaction Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 General client execution rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.1.2.1 Generation of the SQL transaction entity
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .“.
4.1.2.2 Execution of an SQL-statement
4.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.1.5
4.1.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
..............................................................
4.2 The RDA SQL Specialization server execution rules
.................................................................
4.2.1 RDA SQL Specialization dialogue-state model
4.2.1.1 RDA dialogue entity .
..........................................................................................
4.2.1.2 Opened data resource entity
4.2.1.3 Defined DBL Entity .
....................................................................................................
4.2.1.4 RDA operation entity
4.2.2 General server execution rules .
................................................................................
4.2.3 RDA Dialogue Management services
.................................................................
4.2.3.1 RDA Dialogue Initialization functional unit
4.2.3.1.1 R-Initialize Service .
.................................................................
4.2.3.2 RDA Dialogue Termination functional unit
4.2.3.2.1 R-Terminate Service .
............................................................................
4.2.4 RDA Transaction Management services
............................................................ 29
4.2.4.1 RDA Transaction Management functional unit
..................................................................................
4.2.4.1.1 R-Begin Transaction Service
4.2.4.1.2 R-Commit Service .
.................................................................................................
4.2.4.1.3 R-Rollback Service
4.2.5 RDA Control services .
...................................................................................................
4.2.5.1 Cancel functional unit
4.2.5.1.1 R-Cancel Service .
.....................................................................................................
4.2.5.2 Status functional unit
4.2.5.2.1 R-Status Service .
...............................................................................................
4.2.6 Resource Handling services
4.2.6.1 Resource Handling functional unit .
.......................................................................................................
4.2.6.1.1 R-Open Service
4.2.6.1.2 R-Close Service .
..............................................................................................
4.2.7 Database Language services
...................................................................
4.2.7.1 Immediate Execution DBL functional unit
...........................................................................................
4.2.7.1.1 R-ExecuteDBL service
..........................................................................
4.2.7.2 Stored Execution DBL functional unit
............................................................................................
4.2.7.2.1 R-define DBL Service
.............................................................................................
4.2.7.2.2 R-InvokeDBL Service
...............................................................................................
4.2.7.2.3 R-DropDBL Service
. . .
0 ISO/IEC
ISO/IEC 9579-2: 1998(E)
......................................................................... 43
4.3 Structure and Encoding of RDA SQL APDUs
........................................................................................................
4.3.1 Abstract Syntax Name
...........................................................
4.3.2 ASN. I Module for RDA SQL Specialization ASE
4.4 Conformance .
.............................................................................................................
4.4.1 Static conformance
4.4.2 Dynamic Conformance .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 . THE RDA SQL SPECIALIZATION APPLICATION-CONTEXTS
................................................................................
5.1 The RDA SQL Basic application-context
5.1. I RDA SQL Basic application-context object identifier .
................................................... 58
5.1.2 Additional constraints on the RDA SQL ASE datatypes
...............................................................................................
5.1.3 Additional sequencing rules
...............................................................................
5.1.4 Additional conformance requirements
........................................................................................................
5.1.4. I Static conformance
5.1.4.2 Dynamic conformance .
....................................................................................
5.2 The RDA SQL TP application-context
...........................................................
5.2.1 RDA SQL TP application-context object identifier
...................................................
5.2.2 Additional constraints on the RDA SQL ASE datatypes
5.2.3 Additional sequencing rules .
...............................................................................
5.2.4 Additional conformance requirements
5.2.4.1 Static conformance .
5.2.4.2 Dynamic conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Annex A (informative): Encoding of Multiple Rows
iv
ISO/IEC 9579-2: 1998(E)
0 ISO/IEC
Figures
Figure I. Usage of Embedded SQL Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables
................................................................................. 7
Table 1. R-Initialise SQL Specific Service Parameters
....................................................................................
Table 2. R-Cancel SQL Specific Service Parameters
...................................................................................... 8
Table 3. R-Status SQL Specific Service Parameters
.......................................................................................
Table 4. R-Open SQL Specific Service Parameters
I1
Table 5. R-Close SQL Specific Service Parameters .
.........................................................................
Table 6. R-ExecuteDBL SQL Specific Service Parameters
Table 7. R-Define DBL SQL Specific Service Parameters .
...........................................................................
Table 8. R-InvokeDBL SQL Specific Service Parameters
Table 9. SQLDBLStatement .
............................................
Table 10. sQLDBLArgumentSpecification and sQLDBLResultSpecification
Table 11. sQLDBLArgumentValues and sQLDBLResultValues .
.......................................................
Table 12. R-ExecuteDBL use of SQL argument and result parameters
......................................................... 37
Table 13. R-DefineDBL use of SQL argument and result parameters
........................................................
Table 14. R-InvokeDBL use of SQL argument and result parameters

ISO/IEC 9579-2: 1998(E) 0 ISO/IEC
Foreword
IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of IS0 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.
IS0 and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the
work.
In the field of information technology, IS0 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 9579-2 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 2 I, Open systems interconnection, data management and open
distributedprocessing.
This second edition cancels and replaces the first edition (ISO/IEC 9579-2: 1993), which has been
technically revised. It also incorporates Technical Corrigendum 1: 1995.
ISO/IEC 9579 consists of the following parts, under the general title Information technology - Open
Systems Interconnection - Remote Database Access:
- Part I: Generic Model, Service and Protocol
- Part 2: SQL Specialization
Annex A of this part of ISO/IEC 9579 is for information only.
VI
0 ISO/IEC ISO/IEC 9579-2: 1998(E)
Introduction
Remote Database Access (RDA) International Standards are members of a set of International Standards
produced to facilitate the interworking of computer systems. The RDA International Standards are
positioned in the Application Layer of the Reference Model of Open Systems Interconnection (OSI) and
are related to other Open Systems International Standards in the set, as defined in IS0 7498, OSI - Basic
Reference Model.
The goal of Remote Database Access is to allow, with a minimum of technical agreement outside the
interconnection standards, the interconnection of applications and database systems:
l from different manufacturers;
under different managements;
of different levels of complexity;
exploiting different technologies.
An application may itself be a database system and therefore an RDA Specialization standard can be used
to support multi-database system interworking.
This part of ISO/IEC 9579 is to be used together with ISO/IEC 9579-l to provide remote data access to a
database management system conforming to ISO/IEC 9075 (Database Language SQL).
This part of ISO/IEC 9579 is provided for implementators of the protocol and service defined in
ISO/IEC 9579-2: 1993 who wish to upgrade their implementation to support those features of
ISO/IEC 9075: 1992 which are not supported by ISO/IEC 9579-2: 1993. A third edition of this part of
ISOIIEC 9579 is in preparation which will provide enhanced support more appropriate for new
implementations wishing to support ISO/IEC 9075: 1992 in conjunction with ISO/IEC 9075-3: 1995
(SQLKLI).
vii
This page intentionally left blank

INTERNATIONAL STANDARD 0 ISO/IEC ISO/IEC 9579-2: 1998(E)
Information technology - Open Systems Interconnection -
Remote Database Access -
Part 2:
SQL Specialization
1 GENERAL
11 . Scope
This part of ISO/IEC 9579 specifies the functionality of a database server within a distributed open
systems environment and specifies the communication service and protocol for accessing its capabilities.
The communications capabilities are positioned in the Application Layer of the Reference Model for Open
Systems Interconnection (OSI).
This part of ISO/IEC 9579 complements ISO/IEC 9579-l (RDA Generic) in order that the two parts
together:
a) define the capabilities of an RDA SQL database server supporting dialogues with clients.
b) define a model of dialogues between the RDA SQL database server and remote users.
c) define a model of a dialogue between an RDA client and an RDA server.
d) define an abstract service for the RDA SQL ASE, which models the communications facilities
supporting interaction between the RDA client and RDA server.
e) define the RDA SQL ASE protocol to support the RDA SQL Service.
f) define the characteristics of application-contexts which include the RDA SQL ASE.
g) define application contexts that support remote database access using SQL:
1) RDA Basic application-context
2) RDA TP application-context
This part of ISO/IEC 9579 does not specify individual implementations or products, nor does it constrain
the implementation of entities and interfaces within a computer system.
This part of ISO/IEC 9579 does not define a programmatic interface. The RDA server includes a database
capability as defined in ISO/IEC 9075 (Database Language SQL).
Notes:
1 The RDA client may contain an SQL application program but there is no requirement that the RDA client
shall be an application program written to the ISO/IEC 9075 (Database Language SQL) application program
interface.
2 ISO/IEC 9075: 1989, the former International Standard for Database Language SQL, has been replaced by
ISOIIEC 9075: 1992. Both the current and former standards contain conformance rules, and the RDA SQL
Specialization allows an RDA client to specify the desired level of conformance which it expects the RDA
Server to support. Throughout this part of ISO/IEC 9579, “SQL” refers to the language statements permitted
by the appropriate standard at the requested level of conformance.
12 . Normative references
The following standards contain provisions which, through reference in this text, constitute provisions of
this part of ISO/IEC 9579. 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 9579 are encouraged to
investigate the possibility of applying the most recent editions of the standards indicated below. Members
of IEC and IS0 maintain registers of currently valid International Standards.
ISOIIEC 8824: 1990, Information technology - Open Systems Interconnection - Specification of Abstract
Syntax Notation One (ASN.1).
Open Systems Interconnection - Specification of Basic
ISOIIEC 8825: 1990, Information technology -
Encoding Rules for Abstract Syntax Notation One (ASN. I).

ISO/IEC 9579-2: 1998(E) 0 ISOAEC
ISO/IEC 9075: 1992, Information technology - Database languages - SQL.
ISOIIEC 9075-3: 1995, Information technology - Database languages - SQL - Part 3: Call-Level
Interface (SQLKLI).
ISOIIEC 9075-4: 1996, Information technology - Database languages - SQL - Part 4: Persistent Stored
Modules.
ISOIIEC 9579-1: 1993, Information technology - Open Systems Interconnection - Remote Database
Access - Part I: Generic Model, Service and Protocol.
Compatibility
1’3 . . 1 SQL Standards Supported
This part of ISO/IEC 9579 is fully compatible with the following editions and parts of the SQL
International Standard:
l ISO/IEC 9075: 19WSQL87
l ISO/IEC 9075: 1989 SQL89
l ISO/IEC 9075: 1992 SQL92
. ISO/IEC 9075-3: 1995 SQL/CL1
. ISO/IEC 9075-4: 1996 SQL/PSM
1.3.2 Upward Compatibility
This edition of ISO/IEC 9579-2 is upward compatible with ISO/IEC 9579-2: 1993. Where services or
protocols are provided by both this edition and ISO/IEC 9579-2: 1993, these services or protocols behave
in the same manner and provide the same functionality. .
SQL application programs which conform to SQL 87, SQL 89 or SQL 92 entry level should be able to
correctly execute without change in the following configurations:
l ISO/IEC 9579-2: 1993 client and ISO/IEC 9579-2: 1993 server - This is the reference configuration
against which the other cases are compared.
l ISO/IEC 9579-2: 1993 client and ISO/IEC 9579-2: 1997 server - The ISO/IEC 9579 -2: 1997 server
behaves as an ISO/IEC 9579-2: 1993 server.
l ISO/IEC 9579-2: 1997 client and ISO/IEC 9579-2: 1993 server - The ISO/IEC 9579 -2: 1997 client
behaves as an ISO/IEC 9579-2: 1993 client.
l ISO/IEC 9579-2: 1997 client and ISO/IEC 9579-2: 1997 server - This is the configuration provided for
by this standard.
14 . Definitions
For the purposes of this part of ISO/IEC 9579, the definitions given in ISO/IEC 9579-l and the following
definitions apply.
1.4.1 Terms defined in ISO/IEC 9075 (Database Language SQL)
This part of ISO/IEC 9579 makes use of the following terms defined in ISO/IEC 9075: 1989 (Database
Language SQL) or ISO/IEC 9075: 1992 (Database Language SQL).
applicable privileges
catalog
cluster of catalogs
Embedded SQL
ISOLATION LEVEL SERIALIZABLE
READ WRITE
SQLCODE
SQLSTATE
SYSTEM USER
-
ISO/IEC 9579=2:1998(E)
0 ISOIIEC
In addition, this part of ISOIIEC 9579 references the following non-terminal production symbols from the
SQL syntax, which represent a valid string of characters that can be derived from these production
symbols according to the syntax rules in ISOIIEC 9075 (Database Language SQL) at the appropriate level
of conformance.
<1987>
4989>
4992>


















‘0 I. positioned>





collation statement>
















0 ISOIIEC
ISO/IEC 9579-2: 1998(E)


tement>
authoriza tion identifier>

.



(revoke statement>




























1.4.2 Terms defined in this part of ISO/IEC 9579
1.4.2.1 SQL database resource
An SQL cluster of catalogs together with the data described by the schemas of the catalogs of that cluster.
1.4.2.2 RDA SQL statement
One of the non-terminals ,

, , statement>, , , , ,
, , , , statement>, and as defined in ISOIIEC 9075 (Database Language
SQL).
0 ISOIIEC ISO/IEC 9579-2: 1998(E)
15 . Abbreviations
For the purposes of this part of ISOIIEC 9579, the abbreviations given in ISOIIEC 9075 and
ISOIIEC 9579- 1 apply.
16 . Conventions
This part of ISOIIEC 9579 adopts the conventions established in ISOIIEC 9579-l.
The RDA SQL Specialization is formally defined in an ASN.l Module that is derived from the RDA
Specialization module template defined in ISOIIEC 9579-l. The RDA SQL Specialization module
provides definitions for those types listed in the template as being undefined by the Generic part of
ISOIIEC 9579.
The structure of this part of ISOIIEC 9579 follows the requirements defined in ISOIIEC 9579-l for
defining specializations of the RDA Generic Service and Protocol.
In this part of ISOIIEC 9579, the RDA Generic parameters and data types named specificxxxx. and
SpecificXxxx. . are renamed to sQLXXXX. and to SQLXXXX., respectively.
In the service parameter tables in 3.1, parameters which are defined by this specialization have values
entered in the Req, Ind, Rsp or Cnf columns. Other service parameters in these tables which are copied
from the RDA Generic to improve readability do not have entries in these columns.
The RDA SQL Specialization defines a means of communicating SQL database language statements and
their parameters from an RDA client to an RDA server, and of returning the results of those statements.
Database Language SQL is supported at various levels of conformance, determined by an Object Identifier
defined in ISOIIEC 9075
In this part of ISOIIEC 9579, the reference “ISO/IEC 9075 (Database Language SQL)” means any
International Standard carrying the designation ISOIIEC 9075 and year of approval. The specific version
(or versions) of that standard that is intended in each instance is determined, for the RDA client, by the
SQL Conformance Level requested either when the RDA dialogue is initialized or when a data resource is
opened, and, for the RDA server, by the SQL Conformance Level (or Levels) claimed in the Protocol
Implementation Conformance Statement.
When the SQL Conformance Level specifies a year value of 1987 or 1989, the relevant International
Standard is ISOIIEC 9075: 1989; when the SQL Conformance Level specifies a year value of 1992, the
relevant International Standard is ISOIIEC 9075: 1992.
at a
The term “SQL” is used thro ughout in a generic sense, i ntending to cover Database Language
SQL
written within that conformance level
particular conformance level as well as valid statements

0 ISOIIEC
ISO/IEC 9579-2: 1998(E)
2 MODEL
The RDA SQL Specialization Service model
21 .
2.1.1 Mapping to the general model of the RDA Service
This subclause relates the relevant concepts defined in Section 2 of ISOIIEC 9579-l to this RDA SQL
Specialization.
The term data resource, defined in ISOIIEC 9579-l) corresponds to an SQL database resource as
defined in this part of ISOIIEC 9579.
The RDA client gains access to an SQL database resource at the RDA server by opening it. It is then
available for use in requests for Database Language Services (3.1.5 Database Language Services” on
page 11). Nested SQL database resources are not supported.
Closing an SQL database resource causes it to be made inaccessible to the RDA client; that is, unavailable
for subsequent use in requests for Database Language Services.
An implementor shall provide an RDA server at which one or multiple SQL database resources are
available.
2.1.2 Mapping to the Concepts of Database Language SQL
This subclause relates the relevant Concepts defined in clause 4 of ISOIIEC 9075 (Database Language
SQL) to the database model contained in the RDA server.
RDA SQL statements are executed by the database server exactly as if they were embedded in a host
program local to the SQL database resource. Any exception condition or completion condition raised by
the database server is returned to the RDA client.
Note: A RDA SQL statement must have been executed or invoked at the RDA server prior to
executing or invoking any that uses the same cursor name. A or
must have been executed or invoked at the RDA server prior to executing or
invoking any that uses the same .
0 ISOIIEC ISO/IEC 9579-2: 1998(E)
3 SERVICE
31 . The RDA SQL Specialization Service
This clause contains the expansion of the RDA Generic Service parameters which are specialization
defined. These specifications are in addition to those specified in ISOIIEC 9579-l.
Note: The subclauses in this clause are elaborations of the corresponding subclauses in ISO/IEC 9579-I and are
numbered accordingly.
3.1.1 RDA Dialogue Management services
3.1.1.1 RDA Dialogue Initialization functional unit
3.1.1.1.1 R-Initialize Service
Table 1 lists the R-Initialize SQL Specific Service Parameters.
Table 1. R-Initialize SQL Specific Service Parameters
Req Ind Rsp Cnf
Request Parameters
sQLInitializeArgument U
CC=)
sQLConformanceLeve1Default U
cc=>
userData C
CC=)
Result Parameters
sQLInitializeResu1t U
cc=>
userData C
CC=)
Error Parameters
=
SQLInitializeError S
SC >
-
-
characterSetNotSupported S
SC >
Request Parameters
SQLInitializeArgument:
This argument is used to negotiate the level of support desired by the RDA client.
sQLConformanceLevelDefault:
This parameter identifies the characteristics (“SQL level”) of the Database Language SQL requested by
the RDA client. The object identifiers specifying those characteristics are defined in
ISOIIEC 9075: 1992. This is the default SQL Conformance Level requested by the RDA client. If this
parameter is omitted, there is no default established for the RDA client.
userData:
The meaning of this parameter is defined by the implementor of the RDA server.
Result Parameters
SQLInitialize Result:
This parameter contains information returned by the RDA server whose meaning is specific to this
RDA SQL Specialization
userData:
The meaning of this parameter is defined by the implementor of the RDA server.
Error Parameters
SQLInitializeError:
This parameter is used by the RDA server to report errors.
characterSetNotSupported:
This parameter is returned by the RDA server when the RDA server does not support a character set
associated with a character string value received from an RDA client.
3.1.1.2 RDA Dialogue Termination functional unit
3.1.1.2.1 R-Terminate Service
Note: None of the specific request, result or error parameters for this service are used in this Specialization.

0 ISO/IEC
ISO/IEC 9579-2: 1998(E)
RDA Transaction Management services
3J.2
3.1.2.1 RDA Transaction Management functional unit
R-BeginTransaction Service
3.1.2.1.1
Note: There are no specific request, result or error parameters.
R-Commit Service
3.1.2.1.2
Note: There are no specific request, result or error parameters.
3.1.2.1.3 R-Rollback Service
Note: There are no specific request, result or error parameters.
3.1.3 RDA Control Services
3.1.3.1 Cancel functional unit
R-Cancel Service
3.1.3.1.1
Table 2 lists the R-Cancel SQL Specific Service Parameters.
Table 2. R-Cancel SQL Specific Service Parameters
Req Ind Rsp Cnf
Error Parameters
-
-
sQLCancelError S
SC )
-
-
characterSetNotSupported S
SC >
Error Parameters
sQLCancelError:
This parameter is used by the RDA server to report errors.
characterSetNotSupported:
This parameter is returned by the RDA server when the RDA server does not support a character set
associated with a character string value received from an RDA client.
3.1.3.2 Status functional unit
3.1.3.2.1 R-Status Service
Table 3 lists the R-Status SQL Specific Service Parameters.
Table 3. R-Status SQL Specific Service Parameters
Cnf
Req Ind Rsp
Error Parameters
-
-
sQLStatusError S
SC >
-
-
characterSetNotSupported S
so ‘1
Error Parameters
SQLStatusError:
This parameter is used by the RDA server to report errors.
characterSetNotSupported:
This parameter is returned by the RDA server when the RDA server does not support a character set
associated with a character string value received from an RDA client.
3.1.4 Resource Handling services
3.1.4.1 Resource Handling functional unit
3.1.4.1.1 R-Open Service
Table 4 lists the R-Open SQL Specific Service Parameters.
0 ISO/IEC ISO/IEC 9579-2: 1998(E)
[Table 4. R-Open SQL Specific Service Parameters
Ind Cnf
Rsp
Request Parameters
-
-
sQLAccessControlData
cc )
-
-
sQLUsageMode
c( )
SQLOpenArgument
cc=>
-
-
charSet
c( >
-
-
sQLConformanceLeve1
cc )
-
-
sQLDiagnosticsRequested
cc )
-
-
sQLDescriptorStatements
cc >
Result Parameters
-
-
sQLOpenResult U
cc >
-
-
charSet U
cc >
-
-
charSetNotSupported U
cc )
-
-
sQLConformanceLeve1 C
cc )
Error Parameters
-
-
sQLOpenError S
s( >
=
invalidSQLConformanceLeve1 S
SC )
-
-
rDATransactionOpen S
s( >
-
-
sQLAccessControlViolation S
SC >
-
-
sQLDatabaseResourceAlreadyOpen S
SC )
-
-
characterSetNotSuPPorted S
SC )
Request Parameters
dataResourceName:
This parameter (defined in ISO/IEC 9579-l) specifies the of a catalog belonging to an
SQL database resource as defined in this part of ISO/IEC 9579.
sQLAccessControlData:
Data supplied by the RDA client to authenticate the right to open the SQL database resource for the
required usage.
sQLUsageMode:
This argument specifies the access mode to the SQL database resource. If “retrieval” mode is chosen
then all the objects within that SQL database resource can be accessed for read-only purposes and any
attempt to modify any object within that SQL database resource causes an error usageModeViolation.
If “update” mode is chosen then update, insert and delete of the objects within that SQL database
resource are permitted. The applicable privileges as defined in ISO/IEC 9075: 1992 may further restrict
the access to any of the objects within that SQL database resource irrespective of the sQLUsageMode.
The default value for sQLUsageMode is “retrieval”.
Note: The RDA service does not enforce consistency between the SQLUsageModeValue sent on R-Open and the
access mode attributes on a .
SQLOpenArgument:
This parameter contains information sent by the RDA client whose meaning is specific to SQL.
charset:
This parameter uniquely identifies the specification of a coded character set. The character repertoire
for character data associated with (described by) this parameter is the character repertoire specified in
The character set identified by that specification shall
the identified coded character set specification.
be used by the RDA client as the default in this RDA dialogue for all RDA SQL Statements and their
associated character data arguments accessing the SQL database resource opened by this RDA service.
Note: This default can be overridden by explicit specification, in an sQLDBLArgumentSpecification or an
SQLDBLStatement, of a character set for a particular argument value or RDA SQL statement.
If this parameter is omitted, there is no default established for the RDA client.
Note: This means that a charSet parameter must be specified for every character data argument and
SQLDBLStatement sent by the RDA client.

0 ISO/IEC
ISO/IEC 9579-2: 1998(E)
sQLConformanceLeve1:
This parameter identifies the characteristics (“SQL level”) of the Database Language SQL requested by
the RDA client. The object identifiers specifying those characteristics are defined in
ISO/IEC 9075: 1992. This is the sQLConformanceLeve1 which the RDA client requests for all RDA
SQL statements for this SQL database resource. This parameter shall be provided if no default was
established by the RDA client on
...