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
Open System Services Porting Guide—520573-006
Glossary-1
Glossary
absolute pathname. An Open System Services (OSS) pathname that begins with a slash
(/) character and is resolved beginning with the root directory. Contrast with relative
pathname.
address space. The memory locations to which a process has access.
ANSI. The American National Standards Institute.
API. See application program interface (API).
application program interface (API). A set of services (such as programming language
functions or procedures) that are called by an application program to communicate with
other software components. For example, an application program in the form of a client
might use an API to communicate with a server program.
appropriate privileges. An implementation-defined means of associating privileges with a
process for function calls or function call options that need special privileges.
authorization attributes. Security attributes of a process that can change through use of
functions such as setuid() (or of Guardian procedures such as
PROCESS_CREATE_) without reauthentication. The authorization attributes include
the effective user ID, saved-set user ID, saved-set group ID, user audit flags, and the
effective user name.
background process. A process that belongs to a background process group.
background process group. A process group that is both of the following:
•
Not a foreground process group
•
A member of a session that has a connection with a controlling terminal
base computing platform. The minimum software implementation that is the foundation for
the X/Open common applications environment (CAE). See also common applications
environment (CAE).
BSD. Berkeley Software Distribution.
CAE. See common applications environment (CAE).
character. A sequence of one or more bytes representing a single character; used for the
organization, representation, or control of data. A single-byte character consists of
eight bits that represent a character. A multibyte character uses one or more bytes to
represent a character. A wide character is a fixed-width character wide enough to hold
any coded character supported by an implementation.
The ISO C standard defines the term multibyte character; a single-byte character is a
special case of multibyte character.