Open System Services Porting Guide (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to Porting
- 2 The Development Environment
- 3 Useful Porting Tools
- 4 Interoperating Between User Environments
- Purpose of Interoperability
- The OSS User Environment
- OSS Commands for the Guardian User
- Guardian Commands for the UNIX User
- OSS Pathname and Guardian Filename Conversions
- Running the OSS Shell and Commands From TACL
- Running Guardian Commands From the OSS Shell
- Running OSS Processes With Guardian Attributes
- Using OSS Commands to Manage Guardian Objects
- 5 Interoperating Between Programming Environments
- 6 OSS Porting Considerations
- 7 Porting UNIX Applications to the OSS Environment
- 8 Migrating Guardian Applications to the OSS Environment
- General Migration Guidelines
- C Compiler Issues for Guardian Programs
- Using New and Extended Guardian Procedures
- Using OSS Functions in a Guardian Program
- Interoperating With OSS Programs
- Starting an OSS Program From the Guardian Environment
- C Compiler Considerations for OSS Programs
- Porting a Guardian Program to the OSS Environment
- How Arguments Are Passed to the C or C++ Program
- Differences in the Two Run-Time Environments
- Which Run-Time Routines Are Available
- Use of Common Run-Time Environment (CRE) Functions
- Replacing Guardian Procedure Calls With Equivalent OSS Functions
- Which IPC Mechanisms Can Be Used
- Interactions Between Guardian and OSS Functions
- 9 Porting From Specific UNIX Systems
- 10 Native Migration Overview
- 11 Porting or Migrating Sockets Applications
- 12 Porting Threaded Applications
- A Equivalent OSS and UNIX Commands for Guardian Users
- B Equivalent Guardian Commands for OSS and UNIX Users
- C Equivalent Inspect Debugging Commands for dbx Commands
- D Equivalent Native Inspect Debugging Commands for dbx Commands
- E Standard POSIX Threads Functions: Differences Between the Previous and Current Standards
- Glossary
- Index
Glossary
Open System Services Porting Guide—520573-006
Glossary-13
terminal
terminal. A type of character special file that conforms to the interface description in
Clause 7 of ISO/IEC IS 9945-1: 1990.
TNS C compiler. The C compiler that generates TNS object files. TNS object files can be
processed by the Accelerator or Object Code Accelerator to produce accelerated
object files. Compare with TNS/R native C compiler and TNS/E native C compiler.
TNS instructions. Stack-oriented, 16-bit machine instructions that are directly executed on
TNS systems by hardware and microcode. TNS instructions can be emulated on
TNS/E and TNS/R systems by using millicode, an interpreter, and either translation or
acceleration. Contrast with RISC instructions and Intel® Itanium® instructions.
TNS process. A process whose main program object file is a TNS object file, compiled
using a TNS compiler. A TNS process executes in interpreted or accelerated mode
while within itself, when calling a user library, or when calling into TNS system libraries.
A TNS process temporarily executes in native mode when calling into native-compiled
parts of the system library. Object files within a TNS process might be accelerated or
not, with automatic switching between accelerated and interpreted modes on calls and
returns between those parts. Contrast with TNS/R native process and TNS/E native
process.
TNS/E native C compiler. The C compiler that generates TNS/E object files. Contrast with
TNS C compiler and TNS/R native C compiler.
TNS/E native mode. The primary execution environment on a TNS/E system, in which
native-compiled Intel® Itanium® object code executes, following TNS/E native-mode
compiler conventions for data locations, addressing, stack frames, registers, and call
linkage.
TNS/E native object code. The Intel® Itanium® instructions that result from processing
program source code with a TNS/E native compiler. TNS/E native object code
executes only on TNS/E systems, not on TNS or TNS/R systems.
TNS/E native object file. An object file created by a TNS/E native compiler that contains
Itanium instructions and other information needed to construct the code spaces and
the initial data for a TNS/E native process.
TNS/E native process. A process initiated by executing a TNS/E native object file. Contrast
with TNS process and TNS/R native process.
TNS/E native signal. A signal model available to TNS/E native processes in the Guardian
and OSS environments. TNS/E native signals are used for error exception handling.
TNS/E native user library. A user library available to TNS/E native processes in the
Guardian and OSS environments. A TNS/E native user library is implemented as a
TNS/E native dynamic-link library (DLL).
TNS/R native C compiler. The C compiler that generates TNS/R object files. Compare with
TNS C compiler and TNS/E native C compiler.