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-6
internationalization.
internationalization. The process of designing and coding software so that it can be
adapted to meet the needs of different languages, cultures, and character sets, with
the ability to handle various linguistic and cultural conventions. Internationalization
methods enable the processing of character-based data independently of the
underlying character encoding, allowing choice among character sets. Sometimes
referred to as I18N, derived from the 18 letters between the initial I and the final N of
the word internationalization. See also character set.
interoperability. (1) Within an Expand node, the ability to use the features or facilities of
one environment from another. For example, the gtacl command in the OSS
environment allows an interactive user to start and use a Guardian tool in the Guardian
environment.
(2) Among systems from multiple vendors or with multiple versions of operating
systems from the same vendor, the ability to exchange status, files, and other
information. Manuals for the NonStop range of servers often use the term “connectivity”
in this context, while other vendors use “connectivity” to mean hardware compatibility.
ISO. International Organization for Standardization. ISO is an international body that drafts,
discusses, proposes, and specifies standards for network protocols. ISO is best known
for its seven-layer reference model that describes the conceptual organization of
protocols.
ISO is sometimes called the “International Standards Organization”; although ISO is
the official abbreviation, it does not correspond to the organization’s name in any
language.
ISO/IEC-conforming POSIX.1 application. An application that both:
•
Uses only the facilities described in ISO/IEC IS 9945-1:1990 and approved
conforming language bindings for any ISO or IEC standard.
•
Is documented as using only the facilities described in ISO/IEC IS 9945-1:1990
and approved conforming language bindings for any ISO or IEC standard.
Itanium instructions. See Intel® Itanium® instructions
.
job control. The OSS features that allow processes to be stopped, continued, and moved
from or to the background.
link count. The number of directory entries that refer to a particular file.
link name. The filename associated with a specific file within a directory. The length of a
filename, and therefore the length of a link name, depends on the file system. See also
filename.
locale. In localization, the definition of the subset of a user’s environment that depends on
language and cultural conventions.