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-3
DLL.
DLL. See dynamic-link library (DLL)
dynamic-link library (DLL). A collection of procedures whose code and data can be loaded
and executed at any virtual memory address, with run-time resolution of links to and
from the main program and other independent libraries. The same DLL can be used by
more than one process. Each process gets its own copy of DLL static data. Contrast
with shared run-time library (SRL). See also position-independent code (PIC).
empty directory. A directory that contains only an entry for itself and an entry for the
directory directly above it in the hierarchy.
enoft utility. A utility that reads and displays information from TNS/E native object files. See
also noft utility.
feature-test macro. In C and C++ programs, a symbol that, if defined in a program’s source
code, includes specific other symbols from a header within that program’s source code
and makes those symbols visible.
FIFO. A type of special file that is always read and written in a first-in, first-out manner.
FIFO special file. See FIFO.
file. An object to which data can be written or from which data can be read. A file has
attributes such as access permissions and a file type. In the Open System Services
(OSS) environment, file types include regular file, character special file, block special
file, FIFO, and directory. In the Guardian environment, file types include disk files,
processes, and subdevices.
filename. In the OSS environment, a component of a pathname containing any valid
characters other than slash (/) or null. See also file name.
file name. A string of characters that uniquely identifies a file.
In the PC environment, file names for disk files normally have at least two parts (the
disk name and the file name); for example, B:MYFILE.
In the Guardian environment, disk file names include an Expand node name, volume
name, subvolume name, and file identifier; for example,
\NODE.$DISK.SUBVOL.MYFILE.
In the OSS environment, a file is identified by a pathname; for example,
/usr/john/workfile. See also filename.
fileset. In the OSS environment, a set of files with a common mount point within the file
hierarchy. A fileset can be part or all of a single virtual file system.
On an HP NonStop™ system, the Guardian file system for an Expand node has a
mount point and is a subset of the OSS virtual file system. The entire Guardian file
system therefore could be viewed as a single fileset. However, each volume and each
process of subtype 30 within the Guardian file system is actually a separate fileset.