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-14
TNS/R native mode
TNS/R native mode. The primary execution environment on a TNS/R system, in which
native-compiled MIPS object code executes, following TNS/R native-mode compiler
conventions for data locations, addressing, stack frames, registers, and call linkage.
See also TNS/E native mode.
TNS/R native object code. The RISC instructions that result from processing program
source code with a TNS/R native compiler. TNS/R native object code executes only on
TNS/R systems, not on TNS or TNS/E systems.
TNS/R native object file. An object file created by a TNS/R native compiler that contains
RISC instructions and other information needed to construct the code spaces and the
initial data for a TNS/R native process.
TNS/R native process. A process initiated by executing a TNS/R native object file. Contrast
with TNS process and TNS/E native process.
TNS/R native shared run-time library (TNS/R native SRL). A shared run-time library
(SRL) available to TNS/R native processes in the Guardian and OSS environments on
TNS/R systems. TNS/R native SRLs can be either public or private. A TNS/R native
process can have multiple public SRLs but only one private SRL.
TNS/R native signal. A signal model available to TNS/R native processes in the Guardian
and OSS environments. TNS/R native signals are used for error exception handling.
TNS/R native SRL. See TNS/R native shared run-time library (TNS/R native SRL).
TNS/R native user library. A user library available to TNS/R native processes in the
Guardian and OSS environments. A TNS/R native user library is implemented as a
special private TNS/R native shared run-time library (SRL) for non-PIC programs or as
a dynamic-link library (DLL) for PIC programs.
unmount. To make a fileset inaccessible to the users of a node.
user database. A database within an HP NonStop network node that contains the user
name, user ID, group ID, initial working directory, and initial user program for each user
of the node.
user ID. The unique identification of a user within a node.
user name. A string that uniquely identifies a user within the user database for a node.
working directory. In the Open System Services (OSS) environment, a directory,
associated with a process, that is used in pathname resolution for relative pathnames.