ECMA 149 VOL 2-1997 Portable Common Tool Environment (PCTE) - Abstract Specification.pdf

1、Standard ECMA-1494th Edition - December 1997Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chPortable Common ToolEnvironment (PCTE) -Abstract Specification.Standard ECMA-1494th Edition - December 19

2、97Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW ECMA-149.DOC 22-02-99 16,17Portable Common ToolEnvironment (PCTE) -Abstract Specification.Brief History(1) PCTE, Portable Common Tool Environmen

3、t, is an interface standard. The interface is designed tosupport program portability by providing machine-independent access to a set of facilities. Thesefacilities, which are described in this standard, are designed particularly to provide aninfrastructure for programs which may be part of environm

4、ents supporting systems engineeringprojects. Such programs, which are used as aids to systems development, are often referred to astools.(2) PCTE has its origin in the European Strategic Programme for Research and Development inInformation Technology (ESPRIT) project 32, called “A Basis for a Portab

5、le Common ToolEnvironment“. That project produced a specification for a tool interface, an initialimplementation, and some tools on that implementation. The interface specifications wereproduced in the C Language. A number of versions of the specifications were produced,culminating in the fourth edi

6、tion known as “PCTE Version 1.4“. That was in two volumes;volume 2 covered the user interface and volume 1 covered everything else. Subsequently, theCommission of the European Communities (CEC) commissioned Ada versions of the twovolumes of the PCTE specification.(3) The CEC established the PCTE Int

7、erface Management Board (PIMB) in 1986 to maintain PCTEand promote its use. Through its subsidiary PCTE Interface Control Group (PICG) PIMBconducted a widespread public review, and published a revision known as PCTE 1.5.(4) PIMB established an ad hoc task group to consider the form of the standard;

8、this group reported inJune 1988, strongly recommending that the standard should comprise an abstract (language-independent) specification and separate dependent bindings to whatever languages were chosen.(5) In 1986 several nations of the Independent European Programme Group, under Technical Area 13

9、(IEPG TA-13), embarked on a collaborative programme to enhance PCTE to make it equallysuitable for military as for civil use. This project was called PCTE+; the result of the definitionphase was an enhanced specification called PCTE+ issue 3, published in October 1988. Thisconsisted of both Ada and

10、C versions of volume 1, volume 2 being the same as PCTE 1.5 volume2. PCTE+ issue 3 was the basis for the assessment phase, which ended in December 1992. TheECMA PCTE standardization process has benefited greatly from close liaison with the PCTE+programme; in particular through the availability of PC

11、TE+ documents.(6) Upon request from the PIMB, ECMA undertook to continue the development of PCTE to bring itinto a form suitable for publication as an ECMA Standard. ECMA/TC33 was formed in February1988 with this objective. Initially it was intended to base ECMA PCTE on PCTE 1.4, but this wassoon ch

12、anged to PCTE+ issue 3. The report of the PIMB task group on the form of the standardwas accepted by TC33, and a task group (Task Group for ECMA PCTE, TGEP) was formed inNovember 1988, charged with producing the Abstract Specification and bindings for Ada and C.(7) In 1989 attempts were made to stan

13、dardize the user interface of tools on the basis of PCTE 1.4,volume 2. However it soon became apparent that it would be better for PCTE tools to useemerging general-purpose user interface standards, and the issue of a specific PCTE user interfacewas considered out of scope.(8) Following acceptance o

14、f the first edition as an ECMA Standard in December 1990 (and of thebindings in 1991), review by international experts led to the production of second editions of allthree standards. The second editions were accepted by the General Assembly of June 1993, andwere submitted as a draft standard (in 3 p

15、arts) to ISO/IEC JTC1 for fast-track processing tointernational standardization.(9) During the fast-track processing, which was successfully completed in September 1994,comments from National Bodies resulted in a number of changes to the draft standard. Somefurther editorial changes were requested b

16、y JTC1 ITTF. All these were incorporated in thepublished international standard, ISO/IEC 13719, with which the third editions of the ECMAstandards were aligned.(10) This fourth edition incorporates the resolutions of all comments received too late for considerationduring the fast-track processing, o

17、r after, and the contents of Standards ECMA-227 (Extensionsfor Support of Fine-Grain Objects) and ECMA-255 (Object Orientation Extensions). It is alignedwith the second edition of ISO/IEC 13719-1.Adopted as 4th Edition of Standard ECMA-149 by the General Assembly of December 1997.- i -Contents1 Scop

18、e 12 Conformance 12.1 Conformance of binding 12.2 Conformance of implementation 12.3 Conformance of DDL texts and processors 33 Normative references 34 Definitions 44.1 Technical terms 44.2 Other terms 45 Formal notations 56 Overview of PCTE 56.1 PCTE structural architecture 56.2 Object management s

19、ystem 56.3 Object base 66.4 Schema management 66.5 Self-representation and predefined SDSs 76.6 Object contents 76.7 Process execution 76.8 Monitoring 76.9 Communication between processes 86.10 Notification 86.11 Concurrency and integrity control 86.12 Distribution 96.13 Replication 96.14 Security 9

20、6.15 Accounting 106.16 Implementation limits 10- ii -6.17 Support of fine-grain objects 106.18 Support of object-orientation 117 Outline of the Standard 118 Foundation 128.1 The state 128.2 The object base 138.2.1 Objects 138.2.2 Attributes 148.2.3 Links 158.3 Types 168.3.1 Object types 168.3.2 Attr

21、ibute types 178.3.3 Link types 188.3.4 Enumeral types 228.4 Types in SDS 228.4.1 Object types in SDS 248.4.2 Attribute types in SDS 248.4.3 Link types in SDS 248.4.4 Enumeral types in SDS 258.5 Types in working schema 258.5.1 Object types in working schema 268.5.2 Attribute types in working schema 2

22、68.5.3 Link types in working schema 278.5.4 Enumeral types in working schema 278.6 Types in global schema 278.7 Operations 288.7.1 Calling process 288.7.2 Direct and indirect effects 288.7.3 Errors 308.7.4 Operation serializability 319 Object management 329.1 Object management concepts 329.1.1 The b

23、asic type “object“ 329.1.2 The common root 369.1.3 Datatypes for object management 369.2 Link operations 369.3 Object operations 459.4 Version operations 59- iii -10 Schema management 6610.1 Schema management concepts 6610.1.1 Schema definition sets and the SDS directory 6610.1.2 Types 6710.1.3 Obje

24、ct types 6910.1.4 Attribute types 6910.1.5 Link types 7110.1.6 Enumeral types 7210.1.7 Datatypes for schema management 7210.2 SDS update operations 7310.3 SDS usage operations 10110.4 Working schema operations 10811 Volumes, devices, and archives 11311.1 Volume, device, and archiving concepts 11311.

25、1.1 Volumes 11311.1.2 Administration volumes 11411.1.3 Devices 11411.1.4 Archives 11511.2 Volume, device, and archive operations 11612 Files, pipes, and devices 12412.1 File, pipe, and device concepts 12412.2 File, pipe, and device operations 12713 Process execution 13513.1 Process execution concept

26、s 13513.1.1 Static contexts 13513.1.2 Foreign execution images 13613.1.3 Execution classes 13613.1.4 Processes 13713.1.5 Initial processes 14413.1.6 Profiling and monitoring concepts 14413.2 Process execution operations 14513.3 Security operations 15913.4 Profiling operations 16413.5 Monitoring oper

27、ations 16514 Message queues 16714.1 Message queue concepts 167- iv -14.2 Message queue operations 17015 Notification 17615.1 Notification concepts 17615.1.1 Access events and notifiers 17615.1.2 Notification messages 17715.1.3 Time of sending notification messages 17815.1.4 Range of concerned messag

28、e queues 17815.2 Notification operations 17816 Concurrency and integrity control 18016.1 Concurrency and integrity control concepts 18016.1.1 Activities 18016.1.2 Resources and locks 18216.1.3 Lock modes 18516.1.4 Inheritance of locks 18716.1.5 Establishment and promotion of locks 18716.1.6 Implied

29、locks 18916.1.7 Conditions for establishment or promotion of a lock 18916.1.8 Releasing locks 19016.1.9 Permanence of updates 19116.1.10 Tables for locks 19216.2 Concurrency and integrity control operations 19417 Replication 20017.1 Replication concepts 20017.1.1 Replica sets 20017.1.2 Replicated ob

30、jects 20117.1.3 Selection of an appropriate replica 20217.1.4 Administration replica set 20317.2 Replication operations 20318 Network connection 21018.1 Network connection concepts 21018.1.1 Execution sites 21018.1.2 Workstations 21018.1.3 Foreign systems 21318.1.4 Network partitions 21418.1.5 Acces

31、sibility 21418.1.6 Workstation closedown 21618.2 Network connection operations 21718.3 Foreign system operations 222- v -18.4 Time operations 22319 Discretionary security 22519.1 Discretionary security concepts 22519.1.1 Security groups 22519.1.2 Access control lists 22919.1.3 Discretionary access m

32、odes 23119.1.4 Access control lists on object creation 23419.2 Operations for discretionary access control operation 23419.3 Discretionary security administration operations 23820 Mandatory security 24320.1 Mandatory security concepts 24320.1.1 Mandatory classes 24320.1.2 The mandatory class structu

33、re 24520.1.3 Labels and the concept of dominance 24620.1.4 Mandatory rules for information flow 24720.1.5 Multi-level security labels 25120.1.6 Floating security levels 25420.1.7 Implementation restrictions 25620.1.8 Built-in policy aspects 25620.2 Operations for mandatory security operation 25820.3

34、 Mandatory security administration operations 26320.4 Mandatory security operations for processes 26821 Auditing 27021.1 Auditing concepts 27021.1.1 Audit files 27021.1.2 Audit selection criteria 27221.2 Auditing operations 27322 Accounting 27722.1 Accounting concepts 27722.1.1 Consumers and account

35、able resources 27722.1.2 Accounting logs and accounting records 27922.2 Accounting administration operations 28222.3 Consumer identity operations 28723 Common binding features 28823.1 Mapping of types 288- vi -23.1.1 Mapping of predefined PCTE datatypes 28823.1.2 Mapping of designators and nominator

36、s 29023.1.3 Mapping of other values 29823.2 Object reference operations 29923.3 Link reference operations 30123.4 Type reference operations 30524 Implementation limits 30724.1 Bounds on installation-wide limits 30724.2 Bounds on workstation-dependent limits 30924.3 Limit operations 30924.3.1 Datatyp

37、es for limit operations 309Annex A - VDM Specification Language for the Abstract Specification 311Annex B - The Data Definition Language (DDL) 317Annex C - Specification of Errors 327Annex D - Auditable Events 349Annex E - The Predefined Schema Definition Sets 357Annex F - The fine-grain objects mod

38、ule 375Annex G - The object-orientation module 389Index of Operations 413Index of Error Conditions 419Index of Technical Terms 4271Scope(1) This ECMA Standard specifies PCTE in abstract, programming-language-independent, terms. Itspecifies the interface supported by any conforming implementation as

39、a set of abstract operationspecifications, together with the types of their parameters and results. It is supported by a numberof standard bindings, i.e. representations of the interface in standard programming languages.(2) The scope of this ECMA Standard is restricted to a single PCTE installation

40、. It does not specifythe means of communication between PCTE installations, nor between a PCTE installation andanother system.(3) A number of features are not completely defined in this ECMA Standard, some freedom beingallowed to the implementor. Some of these are implementation limits, for which co

41、nstraints aredefined (see clause 24). The other implementation-dependent and implementation-definedfeatures are specified in the appropriate places in this Standard.(4) PCTE is an interface to a set of facilities that forms the basis for constructing environmentssupporting systems engineering projec

42、ts. These facilities are designed particularly to provide aninfrastructure for programs which may be part of such environments. Such programs, which areused as aids to systems development, are often referred to as tools.(5) This ECMA Standard also includes (in annex B) a language standard for the PC

43、TE DataDescription Language (DDL), suitable for writing PCTE schema definition sets.2 Conformance2.1 Conformance of binding(1) A binding conforms to this ECMA Standard if and only if:(2) - it consists of a set of operational interfaces and datatypes, with a mapping from the operationsand datatypes o

44、f this ECMA Standard;(3) - each operation of this ECMA Standard is mapped to one or more sequences of one or moreoperations of the binding (distinct operations need not be mapped to distinct sets of sequencesof binding operations);(4) - each datatype of this ECMA Standard is mapped to one or more da

45、tatypes of the binding;(5) - each named error of this ECMA Standard is mapped to one or more error values (statusvalues, exceptions, or the like) of the binding;(6) - the conditions of clause 23 on common binding features are satisfied;(7) - the conditions for conformance of an implementation to the

46、 binding are defined, areachievable, and are not in conflict with the conditions in 2.2 below.2.2 Conformance of implementation(1) The functionality of PCTE is divided into the following modules:(2) - The core module consists of the datatypes and operations defined in clauses 8 to 19 (except13.1.6,

47、13.4, and 13.5) and 23.- 2 -(3) - The mandatory access control module consists of the datatypes and operations defined inclause 20.(4) - The auditing module consists of the datatypes and operations defined in clause 21.(5) - The accounting module consists of the datatypes and operations defined in c

48、lause 22.(6) - The profiling module consists of the datatypes defined in 13.1.6 and the operations defined in13.4.(7) - The monitoring module consists of the datatype Address defined in 13.1.6 and operationsdefined in 13.5.(8) - The fine-grain objects module consists of the following extensions defi

49、ned in annex F:(9) . extensions to the semantics of operations to cater for fine-grain objects;(10) . new operations;(11) . new error conditions;(12) . additions to the predefined SDS system.(13) - The object-orientation module consists of the following extensions defined in annex G:(14) . additions to the predefined SDSs metasds and system;(15) . an extension to the semantics of the operation SDS_REMOVE_TYPE to cater for the newclasses of type;(16) . new operations;(17) . new error conditions.(18) An implementation of PCTE conforms to this ECMA Standard if and only if it implements thec