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-4
file system
The term file system is often used interchangeably with fileset in UNIX publications.
file system. In the Open System Services (OSS) environment, a collection of files and file
attributes. A file system provides the namespace for the file serial numbers that
uniquely identify its files. Open System Services provides a file system (see also
ISO/IEC IS 9945-1:1990 [ANSI/IEEE Std. 1003.1-1990], Clause 2.2.2.38); the
Guardian application program interface (API) provides a file system; and OSS Network
File System (NFS) provides a file system. (OSS NFS filenames and pathnames are
governed by slightly different rules than OSS filenames and pathnames.) Within the
OSS and OSS NFS file systems, filesets exist as manageable objects.
On an HP NonStop™ system, the Guardian file system for an Expand node is a subset
of the OSS virtual file system. Traditionally, the API for file access in the Guardian
environment is referred to as the Guardian file system.
In some UNIX and NFS implementations, the term file system means the same thing
as fileset. That is, a file system is a logical grouping of files that, except for the root of
the file system, can be contained only by directories within the file system. See also
fileset.
file transfer protocol (FTP). (1) The Internet-standard, high-level protocol for transferring
files from one machine to another. (2) The application used to send complete files over
Transmission Control Protocol/Internet Protocol (TCP/IP) services.
FIPS. A Federal Information Processing Standard of the United States government.
FIPS 151-1. The Federal Information Processing Standard that specifies the requirements
for conformance to an older draft of POSIX.1 than the version adopted as ISO/IEC IS
9945-1:1990 (FIPS 151-1 describes conformance to IEEE Std. 1003.1-1988) and
imposes some additional requirements.
FIPS 151-2. The Federal Information Processing Standard that specifies the requirements
for conformance to POSIX.1 as ISO/IEC IS 9945-1:1990 and imposes some additional
requirements.
foreground process group. A process group whose members have privileges for access
to their controlling terminal that are denied to processes in background process groups
of that terminal. Each session with a controlling terminal has only one foreground
process group for that terminal. Contrast with background process group.
FTP. See file transfer protocol (FTP).
group ID. The nonnegative integer used to identify a group of users of an HP NonStop
network node. Each user of that node is a member of at least one group. When the
identity of a group is associated with a process, a group ID value is referred to as one
of the following identifiers:
•
Real group ID
•
Effective group ID
•
Supplementary group ID