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
Standard POSIX Threads Functions: Differences
Between the Previous and Current Standards
Open System Services Porting Guide—520573-006
E-6
Changed Thread Functions
Table E-4 lists thread functions that have changes to return values only. Errors are
returned as status values, not in errno. Code changes are required if you are porting
an existing threaded application to Standard POSIX Threads.
Table E-4. Thread Functions With Changes to Return Values Only (page 1 of 2)
Function Return Values in Standard POSIX Threads
pthread_cancel() 0 = successful
ESRCH Thread not found.
pthread_cond_
broadcast()
0 = successful
EINVAL The value cond does not refer to an
initialized condition variable.
pthread_cond_destroy() 0 = successful
EBUSY The implementation has detected an attempt
to destroy the object referenced by cond while it
is referenced by another thread.
EINVAL The value specified by cond is invalid.
pthread_cond_signal() 0 = successful
EINVAL The value cond does not refer to an
initialized condition variable.
pthread_cond_signal_
int_np()
0 = successful
EINVAL The address or value specified by cond is
invalid.
pthread_cond_
timedwait()
0 = successful
ETIMEDOUT The time specified by abstime to
pthread_cond_timedwait() has passed.
EINVAL The value specified by cond, mutex, or
abstime is invalid. Different mutexes were
supplied for pthread_cond_timedwait()
operations on the same condition variable. The
mutex was not owned by the current thread at the
time of the call.
pthread_cond_wait() 0 = successful
EINVAL The value specified by cond, mutex, or
abstime is invalid. Different mutexes were
supplied for pthread_cond_timedwait()
operations on the same condition variable. The
mutex was not owned by the current thread at the
time of the call.
pthread_delay_np() 0 = successful
-1 = unsuccessful
(Check errno for last error, such as EINVAL.)