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-6
Process Interoperability
remove(), rename(), tmpfile(), and tmpnam(). Guardian-specific and OSS-
specific versions of these functions are provided for use from the opposite
environment.
Process Interoperability
You create, control, and terminate OSS processes in the OSS environment as you
would in a standard UNIX environment. In addition to the standard set of UNIX
process-management functions in the OSS environment, there are several HP
extension functions that provide flexibility in propagating attributes during process
creation.
OSS processes have a full set of Guardian attributes as well as OSS attributes. Most
Guardian process-management procedures can access OSS processes, and a small
set of OSS process-management functions can access Guardian processes.
The following subsections discuss these topics:
•
Process-Creation Interoperability on page 5-6
•
Process-Management Interoperability on page 5-7
•
Process-Termination Interoperability on page 5-9
Process-Creation Interoperability
Table 5-2 indicates the different ways that processes can be created using Guardian
procedure calls and OSS function calls.
fork() and exec Set of Functions
The Guardian and OSS attributes inherited by the fork() function are defined in the
fork(2) reference page either online or in the Open System Services System Calls
Reference Manual. Many Guardian attributes cannot be specified for the created child
process using the fork() function. Guardian attributes can be specified only when
Table 5-2. Process Creation Comparison
Procedure or Function Caller Parentage
Child
Process
File Open
Feature
fork(), exec set,
tdm_fork(),
tdm_execve set,
tdm_spawn()
OSS OSS PID OSS Parent process
passes
attributes to
child process
PROCESS_LAUNCH_ Guardian or
OSS
Ancestor or
MOM
Guardian None
PROCESS_SPAWN_ Guardian or
OSS
Ancestor or
MOM
OSS Files to open
can be
specified