![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Glossary Runtime services intended for direct access from an Ada application. It consists of Ada Tasking services, used by the compiler to implement Ada tasking constructs, and VADS Exec services, which are called explicitly. The Ada Tasking Layer is implemented using the services of the Ada Kernel Layer.
Various runtime services providing extensions to Ada. The Apex compiler does not automatically generate calls to VADS Exec; applications must access them by making explicit subprogram calls.
A common set of services to support the Ada tasking layer using the disparate services provided by a Target Kernel Layer.
The computer system on which an Ada application executes.
The computer system used to create an Ada application executable.
An Apex product for which the target and host are the same type of computer system, and which may in fact be the same computer system.
An Apex product for which the target and host are of distinct, incompatible types; applications cannot run on the host nor can they be created on the target.
Runtime services which drive the hardware of the computer and its peripherals, either directly, by calling the OS, or a mixture of both.
A target kernel layer with the corresponding Ada kernel layer. As such it implements the Ada Kernel Layer over the hardware of the target.
The general term for the target kernel layer provided by Rational.
Rational Exec Microkernel for POSIX
The version of the microkernel implementing tasking support directly, but implementing other runtime services (e.g. signals, time, delay) using the POSIX API.
Rational Exec Microkernel for Embedded
The version of the microkernel implementing all target kernel services, both tasking and otherwise, by accessing the hardware directly.
A proprietary OS by Wind River Systems Inc. for embedded computer systems which serves as the target kernel layer for Rational Apex Embedded to all target architectures for Tornado.
A standard API for multiprocess operating systems. Unless otherwise noted, this will mean ISO/IEC 9945-1 (ANSI/IEEE Std 1003.1, second edition, 1196-07-12), otherwise referred to as P1003.1c. Implementations of this API serves as part or all of the target kernel layer for Rational Apex to all target architectures for POSIX threads.
That extension of P1003.1 in P1003.1c intended to address real time programming requirements, as described in the Introduction of P1003.1c. These include semaphores, process memory locking, memory mapped files and shared memory, priority process scheduling, realtime signals, timers, interprocess communication, synchronized I/O, and asynchronous I/O.
That extension of P1003.1 in P1003.1c intended to address the need for multiple threads of control within a single process, ad described in the Introduction of P1003.1c. These include thread management and synchronization primitives, as well as harmonization of P1003.1 services to multiple threads of control.
A "thin" interface layer between the Ada kernel for Apex native systems and the POSIX API presented by the OS. Some OS implementations leave out optional parts of the standard, or for historical reasons implement a draft version of P1003.1c. This layer implements the standard calls required by the Ada kernel using non-standard OS services.
A proprietary Microsoft Corp. OS for desktop computers. It serves as the target kernel layer for Rational Apex to Intel Architecture for Windows NT.
Rational Software Corporation http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2002, Rational Software Corporation. All rights reserved. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |