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-12
signal mask
signal mask. The set of signals that are currently blocked from delivery to a specific
process.
snapshot file. See process snapshot file.
socket. An end-point for stream-oriented communication. A socket has a file descriptor.
special character. A character entered from a terminal that has an effect other than being
part of the input stream from that terminal.
static server. In the Guardian environment, a process that runs continuously and provides a
specific service to other processes. A static server differs from a traditional UNIX
demon in that a demon actively looks for tasks to perform, while a static server
performs only tasks brought to its attention by a client (requester) process. See also
demon.
storage pool. A set of physical disk volumes administered as a set of logical disk volumes.
A logical disk volume can span multiple physical disk volumes. When a logical disk
volume becomes full, more physical disk volumes can be added.
strictly conforming POSIX.1 application. An application that requires only the facilities
described in ISO/IEC IS 9945-1: 1990 and the applicable computer language
standards. Such an application must accept any behavior or value described in
ISO/IEC IS 9945-1: 1990 as unspecified or implementation-defined and, for symbolic
constants, accept any value permitted by ISO/IEC IS 9945-1: 1990.
super ID. On HP NonStop systems, a privileged user who can read, write, execute, and
purge all files on the system. The super ID is usually a member of a system-supervisor
group.
The super ID has the set of special permissions called appropriate privileges. In the
Guardian environment, the structured view of the super ID, which is (255, 255), is most
commonly used; in the OSS environment, the scalar view of the super ID, which is
65535, is most commonly used.
SVID. The System V Interface Definition for UNIX, published by AT&T.
SVR4. System V Release 4, a specific implementation of UNIX. See System V.
symbolic link. A type of special file that acts as a name pointer to another file. A symbolic
link contains a pathname and can be used to point to a file in another fileset. Symbolic
links are not included in ISO/IEC IS 9945-1: 1990. Compare to hard link.
system. A single copy of the HP NonStop operating system.
system process. A part of a single copy of the HP NonStop operating system with OSS
interfaces. A system process does not have an OSS process ID.
System V. A version of UNIX developed and marketed originally by AT&T.