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
Open System Services Porting Guide—520573-006
1-1
1 Introduction to Porting
This section provides an introduction to porting applications to the HP NonStop Open
System Services (OSS) environment and contains these topics:
•
Overview of Porting on page 1-1
•
Overview of the OSS Environment on page 1-7
Overview of Porting
The porting process is simple:
1. Clean up code; remove architectural dependencies and nonstandard practices.
2. Compile code.
3. Fix problems found at compile time.
4. Fix segment faults and unaligned accesses. Unaligned accesses are almost
always an indication that logic in the code is incorrect.
5. Recompile the code and repeat the process, if necessary.
Use the information given in the following subsections when you consider porting an
application to the OSS environment:
•
Porting Requires Good Coding Practices on page 1-1
•
You Should Use Portable Application Templates on page 1-1
•
Porting Is Easier When Standards Are Used on page 1-2
Porting Requires Good Coding Practices
Much of the material in this guide is not specific to any one vendor, nor is it specific to
Open System Services. It is simply good, standard coding practice. Commercial texts
that cover similar ground are available. These texts include:
•
The C Programming Language, Second Edition, by Brian W. Kernighan and
Dennis M. Ritchie; Prentice-Hall Software Series, Prentice-Hall, Inc.
•
Portable C and UNIX System Programming, by J.E.Lapin; Prentice-Hall Software
Series, Prentice-Hall, Inc.
•
C Traps and Pit Falls, by Andrew Koenig; Addison-Wesley Publishing Company
For more guidelines on following good programming practices, refer to the C/C++
Programmer’s Guide. Additional commercial texts that describe how to write portable
applications in C are listed under Related Reading on page xv.
You Should Use Portable Application Templates
In general, the more you follow good programming practices, the easier it will be to port
your program to other hardware and software environments. An important