ISO/IEC 9579-1:1993/Cor 1:1995

INTERNATIONAL ORGANIZATION FOR STANDARDlZAT10N ”ME~,4YHAPO~HAfl OPrAHM3AUMFi l-l0 CTAHQAPTM3A~MW ORGANlsATlON INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION ”ME~JIYHAPO~HAF1 3JlEKTPOTEXHMYECKAFl KOMVlCCVlFI- COMMISSION ELECTROTECHNIQUE INTERNATIONALE
Information technology - Open Systems Interconnection -
Remote Database Access -
Part 1:
Generic Model, Service and Protocol
TECHNICAL CORRIGENDUM 1
Technologies de / ‘information - Interconnexion de systbmes ouverts (OS/) - AC&S aux bases de donnees 2 distance -
Partie I: Mod&/e, service et protocole
RECTlFlCATlF TECHNIQUE I
Technical corrigendum 1 to International Standard lSO/lEC 9579-l :I 993 was prepared by Joint Technical Committee ISO/IEC
JTC 1, Information technology.
Contents
In the table of contents, replace the entries for
1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.35, 1.3.6, 1.3.7, 1.38, 1.3.9, 1.3.10,
and 1.3.11 with the following:
“1.3.1 Basic Reference Model (IS0 7498)
1.3.2 Reference Model - Part 3: Naming and Addressing (IS0 7498-3)
I .3.3 Service Conventions (IS0 TR 8509)
1.3.4 Service Definition for the Association Control Service Element (IS0 8649)
1.3 5 Connection Oriented Presentation Service Definition (IS0 8822)
1.3.6 Specification of Abstract Syntax Notation One (ASN. 1) (ISO/IEC 8824)
1.3.7 Application Layer Structure (ISO/IEC 9545)
1.3.8 Remote Database Access - Part 1: Generic Model, Service, and Protocol (ISO/IEC 9579- 1)
1.3.9 Commitment, Concurrency, and Recovery (ISO/IEC 9804)
1.3.10 Distributed Transaction Processing (ISO/IEC 10026- 1)
1.3.11 Reference Model of Data Management (ISO/IEC 10032)”
Renumber 1.3.11.1 through 1.3.11.16 as 1.3.8.1 through 1.3.8.16 and position under 1.3.8 in the contents list.
UDC 681.3.621.39 Ref. No. ISO/IEC 9579~1:1993/Cor.l:1995(E)
Descriptors: data processing, information interchange, network interconnection, open systems interconnection, factual data bases, access,
models, protocols.
0 ISO/IEC 1995
Printed in Switzerland

---------------------- Page: 1 ----------------------
ISO/IEC 9579.1:1993/Cor.l:1995(E) 0 ISO/lEC
1.3 Definitions
Reorder the subclauses of 1.3 and modify the titles of these subclauses as follows:
“1.3.1 Basic Reference Model (IS0 7498)
1.3.2 Reference Model - Part 3: Naming and Addressing (IS0 7498-3)
1.3.3 Service Conventions (IS0 TR 8509)
1.3.4 Service Definition for the Association Control Service Element (IS0 8649)
1.3.5 Connection Oriented Presentation Service Definition (IS0 8822)
1.3.6 Specification of Abstract Syntax Notation One (ASN.l) (ISO/IEC 8824)
1.3.7 Application Layer Structure (ISO/IEC 9545)
1.3.8 Remote Database Access - Part 1: Generic Model, Service, and Protocol (ISO/IEC 9579-l)
1.3.9 Commitment, Concurrency, and Recovery (ISOAEC 9804)
1.3.10 Distributed Transaction Processing (ISOAEC 10026- 1)
1.3.11 Reference Model of Data Management (ISO/IEC 10032)”
Renumber 1.3.11.1 through 1.3.11.16 as 1.3.8.1 through 1.3.8.16.
1.3.1 Basic Reference Model
In the first paragraph of 1.3.1 on page 4, delete item f) and reletter the remaining item as necessary.
1.5.2 Service parameter description
In the definition of “S” on page 10, change “two” to “one ”.
3.1.1.1.1 R-Initialize service
Modify the description of the dialogueIDSuffix parameter to read:
“An identifier that is unique within the scope of the application-entity-invocation (identified by the
dialogueIDClientInvocation parameter) of the RDA client that is requesting initialization of the RDA
dialogue.”
On page 21, move note 3 so that it follows the description of the “controlAuthenticationData” Result parameter,
delete the first sentence of the relocated note, and modify the second sentence to read:
“The mechanism for passing authentication data between RDA clients is beyond the scope of RDA.”
Renumber the notes in 3.1.1.1.1 accordingly.
3.1.5.1.1 R-ExecuteDBL service
In the definition of dataResourceHandle on page 42, modify the second sentence to read:
“This parameter identifies a particular data resource among the set of open data resources.”
3.1.5.2.1 R-DefineDBL service
In the definition of dataResourceHandle on page 45, modify the second sentence to read:
“This parameter identifies a particular data resource among the set of open data resources.”

---------------------- Page: 2 ----------------------
0 ISO/lEC SSQ/lEC 9579=1:1993/Cor1:1995(E)
3.2.1 RDA client sequencing rules
In the last paragraph on page 52, modify the definition of state CN to read:
“CN - Either an R-ExecuteDBL error confirm or an R-InvokeDBL error confirm primitive reporting a
transactionRolledBack error parameter was received.”
In table 15 on page 53:
1) add the note reference “1)” to the cells formed by events R-Commit cnf in state CC and R-Rollback
cnf in state CR.
2) add the note reference “2)” to the cells formed by events R-ExecuteDBL cnf in state CT and
R-InvokeDBL cnf in state CT.
3) add the following within the scope of table 15:
“NOTES
1) The resulting state is CN if an R-ExecuteDBL error confirm or an R-InvokeDBL error confirm
reported a transactionRolledBack error parameter in states CT, CC or CR. Otherwise, the resulting
state is CT.
. 2) The resulting state is CN if an R-ExecuteDBL error confirm or an R-InvokeDBL error confirm
reported a transactionRolledBack error parameter. Otherwise, the resulting state is CT.”
3.2.2 RDA server sequencing rules
On page 54, modify the first paragraph to read:
“The RDA Service is asynchronous; that is, the RDA server may receive other indications before it issues
the response to a previous indication.”
In the last paragraph on page 54, modify the definition of state SN to read:
“SN - Either an R-ExecuteDBL error response or an R-InvokeDBL error response primitive reporting a
transactionRolledBack error parameter was issued.”
In table 16 on page 55:
1) add the note reference “1)” to the cells formed by events R-Commit rsp in state SC and R-Rollback
rsp in state SR.
2) add the note reference “2)” to the cells formed by events R-ExecuteDBL rsp in state ST and
R-InvokeDBL rsp in state ST.
3) add the following within the scope of table 16:
“NOTES
1) The resulting state is SN if an R-ExecuteDBL error response or an R-InvokeDBL error response
reported a transactionRolledBack error parameter in states ST, SC or SR. Otherwise, the resulting
state is ST.
2) The resulting state is SN if an R-ExecuteDBL error response or an R-InvokeDBL error response
reported a transactionRolledBack error parameter. Otherwise, the resulting state is ST.”
4.1.1.2 RDA dialogue entity
In the first paragraph of 4.1.1.2 on page 60, modifiy the first sentence to read:
“An RDA dialogue entity is created upon issuance of an R-Initialize result response, and exists until the
RDA dialogue is terminated.”

---------------------- Page: 3 ----------------------
ISO/IEC 9579~1:1993/Cor.l:1995(E) 0 lSO/IEC
4.1.1.3 Opened data resource entity
In the first paragraph of 4.1.1.3 on page 61, modify the first two sentences to read:
“An opened data resource entity is created upon issuance of an R-Open result response. An opened data
resource entity is deleted by an R-Close result response.”
4.1.1.4 Defined DBL entity
In the first paragraph of 4.1.1.4 on page 61, modify the first two sentences to read:
“A defined DBL entity is created upon issuance of an R-DefineDBL result response. A defined DBL
entity is deleted independently of opened data resource entities upon issuance of an R-DropDBL result
response.”
4.1.2.8 Failure of the RDA dialogue
In the first paragraph of 4.1.2.8 on page 65, modify the first bullet to read:
“Recovery actions are performed as appropriate for the application context (see 5.1.2.2, RDA dialogue
failure, for the RDA Basic application-context; see 10.5.17, A(-P)-ABORT indication or A-RELEASE
(Result = affirmative) response, of ISO/IEC 10026-3 for the RDA TP application-context); and”
4.1.3.1.1 R-Initialize service
replace “If an error is not returned” with “If an error response is not
Under “Entity manipulation rules ”,
returned ”.
Under “Result rules ”, replace “If a result is returned” with “If a result response is returned ”.
Under “Error rules ”, replace “An error shall be returned” with “An error response shall be returned ”.
4.1.3.2.1 R-Terminate service
replace “If an error is not returned” with “If an error response is not
Under “Entity manipulation rules ”,
returned ”.
Under “Error rules” in 4.1.3.2.1, modify the first paragraph to read:
“This part of ISO/IEC 9579 does not specify any error rules for this service.”
4.1.4.1.1 R-BeginTransaction service
Under “Result rules” in 4.1.4.1.1, modify the first paragraph to read:
“This part of ISO/IEC 9579 does not specify any result rules for this service.”
Under “Error rules” in 4.1.4.1.1, modify the first paragraph to read:
“This part of ISO/IEC 9579 does not specify any error rules for this service.”
4

---------------------- Page: 4 ----------------------
0 lSO/IEC ISO/IEC 9579~1:1993/Corl:l995(E)
4.1.4.1.2 R-Commit service
Under “Result rules ”, replace “If a result is returned” with “If a result response is returned ”.
Under “Error rules” in 4.1.4.1.2, modify the first paragraph to read:
“This part of ISO/IEC 9579 does not specify any error rules for this service.”
4.1.4.1.3 R-Rollback service
Under “Result rules” in 4.1.4.1.3, modify the first paragraph to read:
“This part of ISO/IEC 9579 does not specify any result rules for this service.”
Under “Error rules” in 4.1.4.1.3, modify the first paragraph to read:
“This part of ISO/IEC 9579 does not specify any error rules for this service.”
4.1.5.1.1 R-Cancel service
Under “Result rules ”, replace “Any R-Cancel result shall be returned” with “Any R-Cancel result response
shall be returned ”.
Under “Error rules ”, replace “An error shall be returned” with “An error response shall be returned ”.
4.1.5.2.1 R-Status service
Under “Entity manipulation rules” in 4.1.5.2.1, modify the first paragraph to read:
“This part of ISO/IEC 9579 does not specify any entity manipulation rules for this service.”
In the result rules, replace “Any R-Status result shall be returned” with “Any R-Status result response shall
be returned ”.
Under “Result rules ”, replace “If a result is returned” with “If a result response is returned ”.
In the table under “Result rules” on page 70, replace the horizontal lines between the “operationStatus ”,
“operationIDUnknown ”, “awaitingExecution ”, “executing ”, “finished ”, “cancelled” and “aborted”
row entries with blank lines.
Under “Error rules ”, replace “An error shall be returned” with “An error respo
...