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-5
Guardian
•
Saved-set group ID
Guardian. An environment available for interactive or programmatic use with the HP
NonStop operating system. Processes that run in the Guardian environment use the
Guardian system procedure calls as their application program interface; interactive
users of the Guardian environment use the HP Tandem Advanced Command
Language (TACL) or another HP product’s command interpreter. Contrast with Open
System Services (OSS).
Guardian environment. The Guardian application program interface (API), tools, and
utilities.
Guardian services. An application program interface (API) to the HP NonStop™ operating
system, plus the tools and utilities associated with that API. This term is synonymous
with Guardian environment. See also Guardian.
hard link. The relationship between two directory entries for the same file. A hard link acts
as an additional pointer to a file. A hard link cannot be used to point to a file in another
fileset. Contrast with symbolic link.
header. An object that, when specified for inclusion in a program’s source code, causes the
program to behave as if the statement including the header were actually a specific set
of other programming statements. A header contains coded information that provides
details (such as data item length) about the data that the header precedes.
In an OSS program, a header is the name of a file known to the run-time library used
by a process. In a Guardian environment C language program, a header is the file
identifier for a file known to the run-time library used by a process.
HP NonStop™ Open System Services (OSS). The product name for the OSS
environment. See also Open System Services (OSS).
HP NonStop™ operating system. The operating system for HP NonStop systems.
IEC. International Electrotechnical Committee. IEC is a professional organization that
creates or adopts standards for computer hardware, environments, and physical
interconnections.
IEEE. Institute of Electrical and Electronics Engineers. IEEE is a professional organization
whose committees develop and propose computer standards that define the physical
and data link protocols of entities such as communication networks.
Intel® Itanium® instructions. Register-oriented Itanium instructions that are native to and
directly executed by a TNS/E system. Itanium instructions do not execute on TNS and
TNS/R systems. Contrast with TNS instructions and RISC instructions.
TNS Object Code Accelerator (OCA) produces Itanium instructions to accelerate TNS
object code. A TNS/E native compiler produces native-compiled Itanium instructions
when it compiles source code.