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-25
Using HP Extensions
Additional signals defined by HP include:
When a receiving process is terminated with saveabend, a file named ZZSAnnnn (the
saveabend file, also known as a snapshot file) is created in the current directory of the
terminated program if possible. This file is equivalent to the core file created in UNIX
environments.
Using the wait() and waitpid() Functions
The wait() and waitpid() function calls cannot be used to wait for the death of
Guardian processes from the OSS environment. In the OSS environment, wait() and
waitpid() return status information for processes that terminate as a result of
Guardian procedure calls in addition to the status information specified by the POSIX.1
standard. Status is also returned for processes that terminate abnormally resulting from
a situation specific to the NonStop system architecture, such as the failure of the child
process’s processor while the parent process continues to execute.
Using HP Extensions
After a program is ported to the OSS environment, you can take advantage of the
extensions offered in the OSS programming environment, such as:
•
HP extensions to the standard functions (see Using OSS Function Calls on
page 7-19)
•
API interoperability (see Section 5, Interoperating Between Programming
Environments, and the API interoperability tables in the Open System Services
Programmer’s Guide)
•
Guardian C run-time routines in mixed-module programs (see Section 5,
Interoperating Between Programming Environments)
•
Embedded SQL (see the SQL/MP Programming Manual for C or the SQL/MX
Programming Manual for C and COBOL)
•
HP extension functions and Guardian procedure calls (discussed in this
subsection)
SIGABEND Abnormal termination
SIGLIMIT NonStop operating system limits trap
SIGMEMERR Uncorrectable memory error
SIGMEMMGR Memory manager read error
SIGNOMEM No memory available
SIGSTK Stack overflow
SIGTIMEOUT Process loop timeout