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
Contents
Open System Services Porting Guide—520573-006
vi
8. Migrating Guardian Applications to the OSS
Environment (continued)
8. Migrating Guardian Applications to the OSS
Environment (continued)
Communicating With OSS Programs 8-4
Migrating a Guardian Program to the OSS Environment 8-4
C Compiler Issues for Guardian Programs 8-4
Compiler Tools 8-5
Memory Models 8-6
Header Files 8-6
Include File Search Order 8-7
Using Pragmas 8-7
Preprocessor Symbols 8-7
Binding TNS Programs 8-8
Linking Native Programs 8-8
Equivalent OSS Commands for Compiling Guardian Programs 8-8
Using New and Extended Guardian Procedures 8-10
Guardian Security Procedures 8-10
Guardian File System Procedures 8-11
Guardian Process-Management Procedures 8-12
Using OSS Functions in a Guardian Program 8-14
Memory Model to Be Used 8-14
Process Target Type 8-15
Use of Environment-Specific Functions 8-15
Object Type Being Manipulated 8-16
Language or C Environment Type 8-16
API Interoperability 8-17
Side Effects
8-17
Interoperating With OSS Programs
8-17
$RECEIVE 8-18
Using FIFOs 8-18
Using Files 8-19
Using Queue Files 8-19
Using Shared Memory 8-19
Using Semaphores 8-19
Using Intermediate Processes 8-20
Using Signals 8-20
Starting an OSS Program From the Guardian Environment 8-20
Using OSH From TACL 8-21
Using system() in a Guardian Program 8-21