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-2
character set
character set. A finite set of characters (letters, digits, symbols, ideographs, or control
functions) used for the organization, representation, or control of data. See also code
set.
child process. A process created by another process. The creating process becomes the
parent process of the new process. See also parent process.
client application. An application that requests a service from a server application.
Execution of remote procedure calls is an example of such a service.
code set. Codes that map a unique numeric value to each character in a character set,
using a designated number of bits to represent each character. Single-byte code sets
use 7 or 8 bits to represent each character. The ASCII and ISO 646 code sets use 7
bits to represent each character in Roman-based alphabets; these code sets are very
limited and are not appropriate for international use. The single-byte code sets in the
ISO 8859 code sets use 8 bits to represent each character and can therefore support
Roman-based alphabets as well as many others including Greek, Arabic, Hebrew, and
Turkish. Multibyte code sets represent characters that require more than one byte,
such as East Asian ideographic characters.
common applications environment (CAE). A computer environment in which applications
can be ported across all X/Open branded products because of the use of international
and industry standards. A CAE is an open system application development
environment, an open system execution environment, or a combination of the two.
compliance. The testing and verification process that precedes X/Open licensing.
constraint. An object that helps protect the integrity of data in a table by specifying a
condition or conditions that all the values in a particular column of the table must
satisfy. Unlike other SQL objects, a constraint has only an SQL name, not an operating
system name, and a constraint does not have a file label.
core dump file. See process snapshot file or saveabend file
.
core file. See see process snapshot file or saveabend file
.
daemon. See demon.
demon. On a UNIX system, a process that runs continuously to provide a specific service
for other processes. A demon does not have a controlling terminal and is not explicitly
invoked. On an HP NonStop™ system, a demon runs in the OSS environment and
has an OSS process ID. See also static server.
device. A computer peripheral or an object that appears to the application as such. See
also terminal.
directory. A type of OSS special file that contains directory entries which associate names
with files. No two directory entries in the same directory have the same name.