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-7
localization
localization. The process of adapting computer interfaces, data, and documentation to the
culturally accepted way of presenting information in the culture. Sometimes referred to
as “L10N,” derived from the 10 letters between the initial “L” and the final “N” of the
word “localization.”
login. The activity by which a user establishes a locally authenticated identity on an HP
NonStop network node. Each login has one login name.
login name. A user name associated with a session.
manpage. The online file containing a topic that is reference manual information. See
reference page.
man page. The online or hard-copy version of a file that provides reference manual
information. See reference page.
manual page. The online file containing a topic that is reference manual information. See
reference page.
mount. To make a fileset accessible to the users of a node.
mount point. A directory that contains a mounted fileset. The mounted fileset can be in a
different file system.
native-compiled Itanium instructions. See Intel® Itanium® instructions.
native-compiled RISC instructions. See RISC instructions.
native mode. See TNS/R native mode or TNS/E native mode.
native object code. See TNS/R native object code or TNS/E native object code.
native object file. See TNS/R native object file or TNS/E native object file.
native object file tool. See noft utility
or enoft utility..
native process. See TNS/R native process
or TNS/E native process.
native signal. See TNS/R native signal or TNS/E native signal.
noft utility. A utility that reads and displays information from TNS/R native object files.
NonStop operating system. See HP NonStop™ operating system.
object file. A file containing compiled machine instructions for one or more routines. This
file can be an executable loadfile for a program or library or a not-yet-executable linkfile
for some program module.
open file. A file with a file descriptor.