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 User Environments
Open System Services Porting Guide—520573-006
4-3
C Programming and Interoperability
C Programming and Interoperability
Writing C programs for the Open System Services (OSS) environment is nearly
identical to writing C programs for a UNIX environment. Programs must comply with
the ISO/ANSI C standard and can call most of the function calls specified by the
POSIX.1 standard and the XPG4 specifications.
Because the NonStop operating system supports both the OSS and Guardian
environments, you can write programs that manipulate objects in both environments.
The HP C compiler complies with the ISO/ANSI C standard. Any C program that strictly
conforms with this standard and does not use features beyond this standard can
immediately be compiled with the HP C compiler. Programs written in Common C (also
called Kernighan and Ritchie C) must be converted to ISO/ANSI C. Refer to the Open
System Services Programmer’s Guide and the C/C++ Programmer’s Guide for details
about programming for the OSS and Guardian environments. Interoperability
discussions in those guides include:
•
Interoperability between the OSS API and Guardian API (functions and macros in
the OSS and Guardian C run-time libraries)
•
Manipulating OSS and Guardian objects
•
Writing mixed-module programs
See also Section 5, Interoperating Between Programming Environments, for various
topics of interoperability between the OSS and Guardian environments.
Figure 4-1. OSS and Guardian Interoperability
006VST .VSD
OSS
Objects
Guardian
Objects
Guardian
API
OSS
API
Guardian
Process
OSS
Process