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
Interoperating Between Programming Environments
Open System Services Porting Guide—520573-006
5-3
Header Files
Header Files
Header files in the Guardian and OSS environment are stored in different places, but
their contents are identical. In most cases, the names of the header files are similar: for
example, sys/types.h in OSS corresponds to SYSTYPEH in Guardian. Truncation
of some characters before the trailing H is common (as shown in the preceding
example). One anomaly is that cextdecs.h corresponds to CEXTDECS (no trailing H
for historical reasons).
Use of Feature-Test Macros
The C compiler provides feature-test macros, for example: _POSIX_SOURCE,
_POSIX_C_SOURCE, _XOPEN_SOURCE, and _TANDEM_SOURCE. Sometimes
options are also selected by macros. For example, _IGNORE_LOCALE is used in
ctype.h to select C/POSIX locale macros rather than internationalized functions. Use
of these macros determine whether a particular set of features will be included from
header files. Feature-test macros also enable you to check how well a program
compiles.
The C header files contain definitions required by the ISO/ANSI C standard, the
POSIX.1 standard, the POSIX.2 standard, and the XPG4 specifications. You control
visibility of the definitions with feature-test macros. If a program does not conform to
the POSIX-standard or XPG4 specification identifiers made visible by a feature-test
macro, the compiler issues error and warning messages. For more information about
feature-test macros, refer to the C/C++ Programmer’s Guide. See also Defined
Symbols and Header Files on page 7-12.
Table 5-1. Differences Between Guardian and OSS Environments
Guardian Environment OSS Environment
TACL command interface OSS shell for supporting command interface
PARAMs, ASSIGNs, DEFINEs for setting
process environment attributes
args, env for setting process attributes
$RECEIVE for interprocess communication Pipes for interprocess communication
Break key for switching between running
processes
Job control signals for switching between
running processes
System messages and Guardian signals
(except the kill() function)
OSS signals only
PROGID program for process identity setuid() and setgid() functions for
process identity
EDIT files ASCII text files
CRE supports shared access to standard
files
Operating system supports standard file
access