CAN CSA-ISO IEC 13712-1A-2000 Information technology - Remote Operations Concepts model and notation AMENDMENT I Built-in operations.pdf

《CAN CSA-ISO IEC 13712-1A-2000 Information technology - Remote Operations Concepts model and notation AMENDMENT I Built-in operations.pdf》由会员分享，可在线阅读，更多相关《CAN CSA-ISO IEC 13712-1A-2000 Information technology - Remote Operations Concepts model and notation AMENDMENT I Built-in operations.pdf（11页珍藏版）》请在麦多课文档分享上搜索。

1、CSA INTERNATIONAL Amendment 1: 1996 to International Standard ISO/IEC 13712-1:1995 has been adopted without modification as Amendment 1 :2000 to CAN/CSA-ISO/IEC 13712-1-00. This Amendment was reviewed by the CSA Technical Committee on Information Technology (TCIT) under the jurisdiction of the Strat

2、egic Steering Committee on Information Technology and deemed acceptable for use in Canada. March 2000 Amendment 1 :2000 to National Standard of Canada CAN/CSA-ISODEC 1371 2-1 -00 Information technology - Remote Operations: Concepts, model and notation AMENDMENT I : Built-in operations Technologies d

3、e linformation - Operations a distance: Concepts, modde et notation AMENDEMENT 1: Operations integrees (Reaffirmed 2004) Reference number ISO/IEC 1371 2-1 :1995/Amd. 1 :1996iE) ISO/IEC 13712-1:1995/Arnd.l:1994(E) Contents 41 5) 7) Subclause 3.3 _. . . . ._. . . . . . . . . . . . . . . . . . . . . .

4、. . . . . . .* . . . . . . . . . . . . . , ._. Subclause 8.2.1 . Subclause 8.2 .-.*.+ Subclause 10.1 . . . . . . . . . . . . . . . . . . . . . . +, .+ . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5、 . . . . . . . . Subclause 10.5.1 * . . . ._ . . ._. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ._. . . ._. . . . . . . . Subclause 10.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . _. . . . . _. . . . . ._. , . . , . . . . . . . . . . . . . . . . ._.

6、. . . . . . . . . . . . . . . . . ._. . . . . . . . . . . . . . Subclauses 10.6 through 10.16 . Subclauses 10.6 through 10.11 -*.- Annex A . Annex D . . Page i i 2 2 2 2 2 2 4 6 0 ISO/IEC 1996 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized

7、in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the pubIisher. ISO/IEC Copyright Office Case postale 56 . CH-121 I Genkve 20 Switzerland 11 0 ISO/TEC ISO/IEC 13712-1:1995/Amd.l: 1996(E) Foreword IS0 (the International Or

8、ganization for Standardization) and IEC (the Inter- national 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 th

9、e 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 in

10、formation 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 natio

11、nal bodies casting a vote. Amendment 1 to International Standard ISO/IEC 137 12- 1 : 1995 was prepared by Joint TechnicaI Committee ISOAEC JTC l? Information technology, Sub- committee SC 21, Open systems interconnection, data management and open distributed processing, in collaboration with ITU-T.

12、The identical text is published as ITU-T Rec. X.880/Arnd. I. 111 ISOnEC 13712-1: 199YAmd.l: 1996(E) Q ISO/IEC Introduction This amendment to Rec. X.880 I ISO/IEC 13712-1 provides the definition of three built-in operations - Probe, Acknowledge and Cancel - which are of general utility to designers o

13、f ROSE-based applications. iv ISO/IEC 13712-1 : 1995/Amd.1 : 1996 a) INTERNATIONAL STANDARD ITU-T RECOMMENDATION INFORMATION TECHNOLOGY - mMOTE OPERATIONS: CONCEPTS, MODEL AND NOTATION AMENDMENT 1 Built-in operations Subclause 3.3 Add the following new definition immediately after 3.3.7: “3.3.8 the

14、performer.” idempotent: A characteristic of an operation that it can be invoked repeatedly without changing the state of The definitions which follow definition 3.3.8, should be renumbered accordingly. 2) Subclause 8.2.1 Add the following field underlined to the QPERATION information object class: O

15、PERATION := CLASS ” 5) Subclause 10.5.1 Rewrite the no-op OPERA TION definition by adding an additional field (underlined) as follows: 1 :o-op OPERATION := - TRUE ALWAYS RESPONDS FALSE CODE lOCal:-l 6) Subclause 10.5.2 Rewrite 10.5.2 as follows (with the new text underlined): “10.5.2 The operation i

16、s idempotent and does not return.” 7) SubcIauses 10.6 through 10.16 Renumber 10.6 through 10.16 as 10.12 through 10.22 respectively. 8) Subclauses 10.6 through 10.11 Add the following new subclauses numbered 20.6 through 10.11: 10.6 Probe 0.6.1 The probe operation enquires about the outcome of a pre

17、wiusly invoked operation. It is specified as follows: probe OPERATION := ARGUMENT SEQUENCE invokeId IO InvokeId 1 RESULT ENUMERATEDrunning(O), finished(l), unknown(2), .) IDEMPOTENT TRUE CODE lOcak-2 10.6.2 10.6.3 performance is finished, or that it is unknown. There is a single argument, of type In

18、vokeId, which identifies the invoked operation being enquired about. The request always returns a result, which indicates whether the operation invocation is still running, its 2 IT”-T REX. X.880 (1994)/Amd.l (1995 E) ISOmEC 13712-1 : 1995/Amd.l : 1996 (E) NOTE - An invocation may be unknown because

19、 it never happened. or because it has been forgotten by the performer. 10.6.4 The operation is idempotent. 10.6.5 invocation concerned, except if the operation was idempotent. A probe (with a result of finished) causes, as a side effect, the retransmission of any return from the NOTE - This implies

20、that the performer of a non-idempotent operation has to retain the response (result or error) if the probe operation has been included in the operation package. 10.7 Acknowledge 10.7.1 invocation. It is specified as follows: The acknowledge operation acknowledges receipt of the return of some (non-i

21、dempotent) operation acknowledge OPERATION := t ARGUMENT InvokeId RESULT ENUMERATEDacknowledged(O), unknown(l), . IDEMPOTENT TRUE CODE l0al:-3 1 10.7.2 acknowledged. There is a single argument, of type InvokeId, which identifies the invocation whose return is being 10.7.3 or that the operation invoc

22、ation concerned is unknown. The request aIways returns a result, which indicates either that the return is now considered acknowledged, NOTE - An invocation may be unknown because it never happened, or because it has kn forgotten by the performer. 10.7.4 The operation is idempotent. 10.7.5 This oper

23、ation must be included in every operation package which includes the probe operation. 10.8 Probe and Acknowledge 10.8.1 frequently both be needed in a package. It is specified as follows: The ProbeAndAcknowledge operation set comprises the two operations suggested by its name, and wiIl ProbeAndAckno

24、wledge OPERATION := probe I acknowledge) 10.9 Cancel 10.9.1 The cancel operation requests the premature termination of the performance of an operation. Only operations which include the cancelled error (see 10.11) in their &Errors field can be cancelled. It is specified as follows: cancel OPERATION

25、:= ARGUMENT InvokeId IULMYUILNI lKUL CODE laI:-4 1 ITU-T Rec. X.880 (1994)/Amd.l(1995 E) 3 ISO/IEC 13712-1 : 1999Amd.l: 1996 (E) 10.9.2 There is a single argument, of type InvokeId, which identifies the invoked operation being cancelled. 10.9.3 10.9.4 The operation is idempotent. Should the request

26、fail, a cancelFailed error (see 10.10) will be returned. 10.10 Cancel failed 10.10.1 A cancelFailed error reports a problem in performing a cancel. It is specified as follows: cancelFded ERROR := I PAWTER SET IO CancelProblem, I CODE local:-2 problem operation 111 InvokeId 1 CanceIProblem := ENUMERA

27、TED unknownOperation( 0), tooLa te( l), operatioflo tCancellable(2), . 10.10.2 The various parameters have the meaning as defined in 10.10.2.1 and 10.10.2.2. 10.10.2.1 The particular problem encountered with cancellation is indicated from the following possibilities: a) unknownoperation - This opera

28、tion invocation has either not happened, or has been forgotten. b) tooLate - The operation has already been performed, or the execution is at a stage that does not permit a cancellation. c) operationNotCancellable - The operation that was invoked was not one of those able to be cancelled. 10.10.2.2

29、The identification of the operation (invocation) which was to be cancelled. 10.11 Cancelled The cancelled error is reported if some operation is cancelled. The error must be included in the &Errors field of the affected operation. It is specified as follows: I cancelled ERROR := CODE 10cal:3 9) Anne

30、x A Change the_first module reference as follows (with the change underlined): Remote-Operations-Information-Ojeects (joint-iso-itu-t remote-operations(4) informationObjects(5) versioa 4 ITU-T Rec. X.880 (1994)/Amd.l(1995 E) ISO/IEC 13712-1 : 19WAmd.l 1996 (E) Add the following Feld (underlined) to

31、the OPERATION infonnarion object class: OPERATION := CLASS &ArgumentType OPTIONAL, &argumentTypeOptional BOOLEAN OPTIONAL, &returnResult &ResultT ype &resul tTypeOptiond &Errors &Linked &synchronous &alwaysReturns &InvokePriority &ResultPriority &operationcode I WITH SYNTAX ARGUMENT RETURN RESULT RE

32、SULT ERRORS LINKED SYNCHRONOUS lIDEMPOTENT ALWAYS RESPONDS INVOKE PRIORITY CODE RESULT-PRIORITY 1 BOOLEAN DEFAULT TRUE, OPTIONAL, BOOLEAN OPTIONAL, ERROR OPTIONAL, OPERATION OPTIONAL, BOOLEAN DEFAULT FALSE, BOOLEAN DEFAULT TRUE, Priority OPTIONAL, Priority OPTIONAL, Code UNIQUE OPTIONAL I &ArgumentT

33、ype OPTIONAL &returnResul t &ResuItType OPTIONAL &Errors &Linked &synchronous &alwaysReturns &InvokePriori ty &ResultPriority &operationCode otentl &argumentTypeOptionalII &resultT ypeOptionaI I Change fhe third module reference as follows (with the change underlined): Remote-Operations-Useful-Defin

34、i tions Cjoint-iso-itu-t remote-operations(4) useful-definitions(7) versiom Change the no-op OPERATION definition by adding an additional field (underlined) as follows: IDEMPOTENT TRUE ALWAYS RESPONDS FALSE no-op OPERATION := CODE lOCal:-l 1 I ITU-T Rec. X.880 (1994)/Amd.l(1995 E) 5 ISO/IEC 13712-1

35、: 1995/Amd.I : 1996 (E) Add the following new items to this module: probe OPERATION := ARGUMENT SEQUENCE invokeId O InvokeId 1 1 ENUMERATEDrunning(O), finished(l), unknown(2), .) RESULT IDEMPOTENT TRUE CODE local:-2 1 acknowledge OPERATION : : = ARGUMENF Invokeld RESULT ENUMERATEDacknowledged(O), un

36、known( l), . IDEMPOTENT TRUE CODE 10cd:-3 1 ProbeAndAcknowledge OPERATION := probe I acknowledge cancel OPERATION := t ARGUMENT LnvokeId ERRORS (cancelFailed IDEMPOTENT TRm CODE local:-4 1 cancelFaiied ERROR := PARAMETER SET problem EO CancelProblem, Operation I InvokeId 1 CODE locak-2 1 CanceiProbl

37、em := ENUMERATED (unknownOperation(O), tooLate(l), operationNotCancellable(2), . cancelled ERROR := CODE iocak-3) 10) AnnexD Make the following changes to the table (with the changes underlined): Clause Object Identifier Value Annex A Cjoint-iso-itu-t remote-operations(4) informationobj ects(5) versiorn Cjoint-iso-itu-t remote-operations(4) usefuLdefinitions(7) versiom 6 ITU-T Rec. X.880 (1994)/Amd.l (1995 E) ICs 35-240.20 Descriptors: data processing, information interchange, network interconnection, teleprocessing, interaction, models, concepts,