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-8
open file description
open file description. A data structure within an HP NonStop Expand network node that
contains information about the access of a process or of a group of processes to a file.
An open file description records such attributes as the file offset, file status, and file
access modes. An open file description is associated with only one open file but can be
associated with one or more file descriptors.
open system. A system with interfaces that conform to international computing standards
and therefore appear the same regardless of the system’s manufacturer. For example,
the OSS environment on HP NonStop systems conforms to international standards
such as ISO/IEC IS 9945-1:1990 (ANSI/IEEE Std. 1003.1-1990, also known as
POSIX.1), national standards such as FIPS 151-2, and portions of industry
specifications such as the X/Open Portability Guide Version 4 (XPG4).
Open System Services (OSS). An open system environment available for interactive or
programmatic use with the HP NonStop operating system. Processes that run in the
OSS environment use the OSS application program interface; interactive users of the
OSS environment use the OSS shell for their command interpreter. Synonymous with
Open System Services (OSS) environment. Contrast with Guardian.
Open System Services (OSS) environment. The HP NonStop Open System Services
(OSS) application program interface (API), tools, and utilities.
Open System Services (OSS) Monitor. A Guardian utility that accepts requests through an
interactive interface named the Subsystem Control Facility (SCF).
Open System Services (OSS) signal. A signal model defined in the POSIX.1 specification
and available to TNS processes and TNS/R native processes in the OSS environment.
OSS signals can be sent between processes.
OSS. See Open System Services (OSS).
OSS environment. See Open System Services (OSS) environment.
OSS Monitor. See Open System Services (OSS) Monitor
.
OSS personality. See Open System Services (OSS) environment
.
OSS process ID (PID). The unique identifier that represents a process during the lifetime of
the process and during the lifetime of the process group of that process. See also PID.
OSS signal. See Open System Services (OSS) signal.
parent process. The process that created a given process, or (if that process has stopped)
a process that has inherited a given process. See also child process
.
pathname. In the OSS file system and Network File System (NFS), the string of characters
that uniquely identifies a file within its file system. A pathname can be either relative or
absolute. See also ISO/IEC IS 9945-1:1990 (ANSI/IEEE Std. 1003.1-1990 or
POSIX.1), Clause 2.2.2.57.