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-11
root directory
Accelerator-generated RISC instructions are produced by accelerating TNS object
code using the Accelerator program (AXCEL). Native-compiled RISC instructions are
produced by compiling source code with a TNS/R native compiler.
root directory. A directory associated with a process that the system uses for pathname
resolution when a pathname begins with a slash (/) character.
saveabend file. A file containing dump information needed by the system debugging tool. In
UNIX systems, such files are usually called core files or core dump files. A saveabend
file is a special case of a save file. See also save file and process snapshot file.
save file. A file created by the Inspect subsystem in response to a command from a
debugger. A save file contains enough information about a running process at a given
time to restart the process at the same point in its execution. A save file contains an
image of the process, data for the process, and the status of the process at the time
the save file was created.
A save file can be created through an Inspect SAVE command at any time. A save file
called a saveabend file can be created when a process’s SAVEABEND attribute is set
and the process terminates abnormally. Other debuggers can create a save file but
refer to the result as a process snapshot file. See also process snapshot file.
server application. An application that provides a service to a client application. Execution
of remote procedure calls is an example of such a service.
session. A set of process groups associated for job control purposes. A session can have a
controlling terminal.
session leader. The process that created a session.
session lifetime. The period that begins when a session is created and ends when the
lifetime of the last remaining process group of the session ends.
shared run-time library (SRL). A collection of procedures whose code and data can be
loaded and executed only at a specific assigned virtual memory address (the same
address in all processes). SRLs use direct addressing and do not have run-time
resolution of links to and from the main program and other independent libraries.
Contrast with dynamic-link library (DLL).
signal. The method by which an environment notifies a process of an event.
signal delivery. The time when Open System Services takes the action appropriate for a
specific process and a specific signal.
signal generation. The time when an event occurs that causes a signal for a process.
signal handler. A function that is executed when a specific signal is delivered to a specific
process.