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-9
pathname component
pathname component. See filename.
pathname resolution. In the OSS environment, the process of associating a single file with
a specified pathname.
pathname-variable limits. Limits that can vary within the OSS file hierarchy. That is, the
limits on a pathname variable can vary according to the directory in which pathname
resolution begins.
path prefix. In the OSS environment, a pathname, with an optional final slash (/) character,
that refers to a directory.
PIC. See position-independent code (PIC).
PID. In the Open System Services (OSS) environment, a synonym for process ID. OSS
process ID is the preferred term in HP NonStop™ system publications.
In the Guardian environment, PID is sometimes used to mean either:
•
A Guardian process identifier such as the process ID
•
The cpu, pin value that is unique to a process within an Expand node.
See also OSS process ID (PID).
pipe. An unnamed FIFO, created programmatically by invoking the pipe() function or
interactively with the shell pipe syntax character (|). A shell pipe redirects the standard
output of one process to become the standard input of another process. A
programmatic pipe is an interprocess communication mechanism.
portable application. An application that can execute on a wide range of hardware
systems from multiple manufacturers. A portable application is a program that can be
moved with little or no change in its source code from another manufacturer’s system
to an HP NonStop system.
position-independent code (PIC). position-independent code (PIC). Executable
program or library code that is designed to be loaded and executed at any virtual
memory address, without any modification. Addresses that can be modified by the
loader do not appear in PIC code, only in data that can be modified by the loader. See
also dynamic-link library (DLL)
POSIX. The Portable Operating System Interface, as defined by the Institute of Electrical
and Electronics Engineers (IEEE) and the American National Standards Institute
(ANSI). Each POSIX interface is separately defined in a numbered ANSI/IEEE
standard or draft standard. The application program interface (API), known as
POSIX.1, has become ISO/IEC IS 9945-1: 1990.
process. (1) A program that has been submitted to the operating system for execution, or a
program that is currently running in the computer. (2) An address space, a single