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
Porting UNIX Applications to the OSS Environment
Open System Services Porting Guide—520573-006
7-14
Defined Symbols and Header Files
_XOPEN_SOURCE When defined, all symbols defined by POSIX.1,
POSIX.2, and XPG4 are visible. The pragma
SYSTYPE OSS defines the _XOPEN_SOURCE
macro.
_XOPEN_SOURCE_EXTENDED When defined, all symbols defined by POSIX.1,
POSIX.2, XPG4, and XPG4 Version 2 are
visible. Because the pragma SYSTYPE OSS
defines the _XOPEN_SOURCE macro, the OSS
user must explicitly define
_XOPEN_SOURCE_EXTENDED to use the
XPG4V2 functions, such as strdup(),
readlink(), symlink(), and others.
Note that, even though the OSS sockets APIs
are defined in Version 1 of the XPG4
specification, you must define
_XOPEN_SOURCE_EXTENDED to use them.
_TANDEM_SOURCE When defined, all symbols defined by HP are
visible. The pragma SYSTYPE GUARDIAN
defines the _TANDEM_SOURCE macro.
__cplusplus The TNS/R and TNS/E native compilers define
this macro, signifying that they are invoked as
C++ compilers instead of as C compilers. The
user does not explicitly define this macro but
chooses it when supplying the file suffix of the
source code; for instance, .C or .cpp means the
file is compiled with the C++ compiler. (Note that
there are two underscores, “__”, before
“cplusplus.”)
Refer to the c89(1) reference page either
online or in the Open System Services Shell and
Utilities Reference Manual for acceptable file
suffixes on input files for the c89 utility.