ISO-13719-3-1998.pdf
B C Reference number ISO/IEC 13719-3:1998(E) INTERNATIONAL STANDARD ISO/IEC 13719-3 Second edition 1998-10-01 Information technology Portable Common Tool Environment (PCTE) Part 3: Ada programming language binding Technologies de l'information Environnement doutil courant portable (PCTE) Partie 3: Liant de langage de programmation Ada Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 01:56:39 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 13719-3:1998(E) © 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 Case postale 56 CH-1211 Genève 20 Switzerland Printed in Switzerland ii Contents 1 Scope1 2 Conformance1 3 Normative references1 4 Definitions2 5 Formal notations2 6 Outline of the Standard2 7 Binding strategy2 7.1 Ada programming language standard2 7.2 General principles2 7.3 Dynamic memory management3 7.4 Complex entities as parameters4 7.5 Character strings4 7.6 Error conditions4 7.7 Implementation limits4 8 Datatype mapping5 8.1 Mapping of PCTE datatypes to LI datatypes5 8.1.1 Mapping of predefined PCTE datatypes5 8.1.2 Mapping of private PCTE datatypes6 8.1.3 Mapping of complex PCTE datatypes7 8.1.4 New LI datatype generators7 8.2 Mapping of LI datatypes to Ada datatypes8 8.2.1 LI datatype: boolean8 8.2.2 LI datatype: pcte-integer8 8.2.3 LI datatype: pcte-natural9 8.2.4 LI datatype: pcte-float9 8.2.5 LI datatype: pcte-time10 8.2.6 LI datatype: octet10 8.2.7 LI datatype: pcte-text11 8.2.8 LI datatype generator: pcte-sequence11 8.2.9 LI datatype generator: bounded-set14 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 01:56:39 MDTNo reproduction or networking permitted without license from IHS -,-,- © ISO/IECISO/IEC 13719-3:1998(E) iii 8.2.10 LI datatype: record15 8.2.11 LI datatype: private16 8.2.12 LI enumerated datatype: pcte-xxx16 8.3 Deriving Ada subprogram semantics from the abstract specification16 8.4 Package Pcte17 9 Object managment36 9.1 Object management datatypes36 9.2 Link operations36 9.3 Object operations40 9.4 Version operations49 10 Schema management51 10.1 Schema management datatypes52 10.2 Update operations53 10.3 Usage operations59 10.4 Working schema operations61 11 Volumes, devices, and archives63 11.1 Volume, device, and archive datatypes63 11.2 Volume, device, and archive operations64 12 Files, pipes, and devices69 12.1 File, pipe, and device datatypes70 12.2 File, pipe, and device operations70 13 Process execution73 13.1 Process execution datatypes73 13.2 Process execution76 13.3 Security operations79 13.4 Profiling operations81 13.5 Monitoring operations81 14 Message queues82 14.1 Message queue datatypes83 14.2 Message queue operations85 15 Notification88 15.1 Notification datatypes88 15.2 Notification operations88 16 Concurrency and integrity control89 16.1 Concurrency and integrity control datatypes89 16.2 Concurrency and integrity control operations89 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 01:56:39 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 13719-3:1998(E) © ISO/IEC iv 17 Replication91 17.1 Replication datatypes91 17.2 Replication operations91 18 Network connection92 18.1 Network connection datatypes93 18.2 Network connection operations93 18.3 Foreign system operations95 18.4 Time operations95 19 Discretionary security95 19.1 Discretionary security datatypes95 19.2 Discretionary access control operations98 19.3 Discretionary security administration operations99 20 Mandatory security101 20.1 Mandatory security datatypes101 20.2 Mandatory security operations101 20.3 Mandatory security administration operations102 20.4 Mandatory security operations for processes104 21 Auditing105 21.1 Auditing datatypes105 21.2 Auditing operations114 22 Accounting119 22.1 Accounting datatypes119 22.2 Accounting operations122 22.3 Consumer identity operations124 23 References124 24 Limits124 25 Errors126 Annex A - The object orientation module137 Index of abstract operations147 Index of Ada subprograms153 Index of Ada datatypes159 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 01:56:39 MDTNo reproduction or networking permitted without license from IHS -,-,- © ISO/IECISO/IEC 13719-3:1998(E) v Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO 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. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO 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 13719-3 was prepared by ECMA (as Standard ECMA-162) and was adopted, under a special “fast-track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies of ISO and IEC. This second edition cancels and replaces the first edition (ISO/IEC 13719-3:1995), which has been technically revised. ISO/IEC 13719 consists of the following parts, under the general title Information technology - Portable Common Tool Environment (PCTE): Part 1: Abstract specification Part 2: C programming language binding Part 3: Ada programming language binding Part 4: IDL binding (Interface Definition Language) Annex A forms an integral part of this part of ISO/IEC 13719. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 01:56:39 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 01:56:39 MDTNo reproduction or networking permitted without license from IHS -,-,- INTERNATIONAL STANDARD © ISO/IECISO/IEC 13719-3:1998(E) 1 Information technology Portable Common Tool Environment (PCTE) Part 3: Ada programming language binding 1Scope This part of ISO/IEC 13719 defines the binding of the Portable Common Tool Environment (PCTE) interfaces, as specified in ISO/IEC 13719-1, to the Ada programming language. A number of features are not completely defined in ISO/IEC 13719-1, some freedom being allowed to the implementor. Some of these features are specified as implementation limits. Some constraints are placed on these implementation limits by this part of ISO/IEC 13719. These constraints are specified in clause 24. PCTE is an interface to a set of facilities that forms the basis for constructing environments supporting systems engineering projects. These facilities are designed particularly to provide an infrastructure for programs which may be part of such environments. Such programs, which are used as aids to system development, are often referred to as tools. 2Conformance An implementation of PCTE conforms to this part of ISO/IEC 13719 if it conforms to 2.2 of ISO/IEC 13719-1, where the binding referred to there is taken to be the Ada language binding defined in clauses 1 to 5 and 8 to 25 of this part of ISO/IEC 13719. All other parts of this part of ISO/IEC 13719 are provided as assistance to the reader and are not normative. The Ada language binding defined in this part of ISO/IEC 13719 conforms to 2.1 of ISO/IEC 13719-1. 3Normative references The following standards contain provisions which, through reference in this text, constitute provisions of this part of ISO/IEC 13719. 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 13719 are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. Members of IEC and ISO maintain registers of currently valid International Standards. ISO/IEC 13719-1:1998,Information technology - Portable Common Tool Environment (PCTE) - Part 1: Abstract specification. ISO/IEC 13719-2:1998,Information technology - Portable Common Tool Environment (PCTE) - Part 2: C programming language binding. ISO 8601:1988,Data elements and interchange formats - Information interchange - Representation of dates and times. ISO/IEC 8652:1995,Information technology - Programming languages - Ada. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 01:56:39 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 13719-3:1998(E) © ISO/IEC 2 ISO/IEC TR 10182:1993,Information technology - Programming languages, their environments and system software interfaces - Guidelines for language bindings. ISO/IEC 11404:1996,Information technology - Programming languages, their environments and system software interfaces - Language-independent datatypes. 4Definitions All technical terms used in this part of ISO/IEC 13719, other than a few in widespread use, are defined in the body of this part of ISO/IEC 13719 or in the referenced documents. 5Formal notations All datatypes and subprogram definitions are expressed using ISO/IEC 8652 conformant syntax. 6Outline of the Standard Clause 7 describes the strategy used to develop this binding specification. Clause 8 defines the mapping from the datatypes that are used in the abstract specification to Ada programming language datatypes. Clauses 9 to 22 define the bindings of datatypes and operations in the corresponding clauses of ISO/IEC 13719-1. The extensions for fine-grain objects are added at the end of clause 11. Clause 23 defines the binding of object and type references, as specified in ISO/IEC 13719-1 23.1.2 and 23.2. Because of the package structure, this clause consists of a cross-reference to the definitions which are in 8.4. Clause 24 defines the binding of the implementation limit subprograms described in ISO/IEC 13719-1, clause 24. Clause 25 defines the binding of the error conditions specified in ISO/IEC 13719-1, clause 25, and defines binding-defined error conditions for the Ada binding. Annex A, which is normative, contains the extensions for object orientation, corresponding to annex G of ISO/IEC 13719-1. 7Binding strategy 7.1Ada programming language standard The Ada package specifications were designed to conform to ISO/IEC 8652. 7.2General principles The following general principles were applied when generating the binding in this part of ISO/IEC 13719. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 01:56:39 MDTNo reproduction or networking permitted without license from IHS -,-,- © ISO/IECISO/IEC 13719-3:1998(E) 3 ISO/IEC TR 10182 should be followed as far as possible for binding method 1: provide a completely defined procedural interface. Each operation in ISO/IEC 13719-1 should be represented by one subprogram in this part of ISO/IEC 13719 unless there are specific reasons to the contrary. All Ada identifiers should be in lower case except for predefined identifiers, named constant values, and enumeration literals. Since the Ada standard is insensitive to case this is for typographical consistency between ISO/IEC 13719-1, ISO/IEC 13719-2, and this part of ISO/IEC 13719. Nondefining occurrences of the names of Ada subprograms and types should use the fully qualified form, so as to identify all package dependences. All the Ada packages should have names that begin with 'Pcte_' to ensure they are unique within an Ada Library System. The choice of case of the characters of 'Pcte' is for typographical consistency with ISO/IEC 13719-2. An abstract operation with name of the form 'TYPE_VERB_PHRASE' should be mapped to an Ada subprogram 'verb_phrase' declared by a package called 'Pcte_type'. For example, 'PROCESS_SET_WORKING_SCHEMA' is mapped to 'Pcte_process.set_working_schema' When a package hierarchy is required, it should be compatible with the abstract specification clause organisation. For example, 'ACCOUNTING_LOG_READ' is mapped to 'Pcte_accounting.log.read'. Names should be retained from ISO/IEC 13719-1 as far as possible. All additional names should be chosen appropriately for their meanings. Each operation that can return errors should have an additional in parameter of an access type designating an object into which error indications can be returned. This allows the subprograms to be procedures or functions as appropriate. Wherever practical, types introduced for passing complex data entities between a caller and a subprogram should be private or limited private. Limited private types should be used unless the basic operations on entities of such types are safe and consistent with ISO/IEC 13719-1. All simple parameter types in ISO/IEC 13719-1 that represent attribute value types should be mapped to corresponding Ada types defined by this binding. All simple parameter types in ISO/IEC 13719-1 that do not represent attribute value types should be mapped to predefined types or subtypes or derived types of predefined types. 7.3Dynamic memory management A type defined in this part of ISO/IEC 13719 for which an object is created dynamically is always limited private, and subprograms are provided to construct, ac
