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
viii
11. Porting or Migrating Sockets Applications
Native Environment Features (continued)
Native Shared Run-Time Libraries 10-3
Dynamic-Link Libraries 10-3
Signal Handling for Guardian Processes 10-4
OSS and Guardian API Interoperability 10-4
C Development Tools 10-4
User Library Migration Issues 10-5
C Language Compilers 10-6
Using the C Run-Time Library 10-7
Obsolete Library Functions 10-7
Changes to the exit() Function 10-8
Changes to the Scanset 10-8
Checking the Condition Code 10-8
Signal Mask Width 10-8
Memory Attributes 10-9
Using Common Run-Time Environment (CRE) Functions 10-9
Guardian Procedure Features 10-9
TAL to pTAL Conversion 10-10
11. Porting or Migrating Sockets Applications
Porting UNIX Sockets Applications to the OSS Environment 11-1
General Considerations 11-1
Differences Between OSS Sockets and Berkeley Software Distribution
Sockets 11-2
Porting Situations 11-3
Porting Guardian Sockets Applications to the OSS Environment 11-4
General Considerations
11-4
Differences Between OSS Sockets and Guardian Sockets
11-5
Compiling Native and TNS OSS Programs 11-7
Interoperability of OSS and Guardian Sockets in an OSS Application 11-8
12. Porting Threaded Applications
Change in Error Reporting 12-1
Considerations for Porting DCE Threads to Standard POSIX Threads 12-1
General Considerations for Porting to Standard POSIX Threads 12-2