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-7
Changed Thread Functions
pthread_get_
expiration_np()
0 = successful
-1 = unsuccessful
(Check errno for last error, such as EINVAL.)
pthread_join() 0 = successful
EINVAL The implementation has detected that the
value specified by thread does not refer to a
thread that can be joined.
ESRCH No thread could be found corresponding to
that specified by the given thread ID.
EDEADLK A deadlock was detected, or the value of
thread specifies the calling thread.
pthread_mutex_
destroy()
0 = successful
EBUSY The implementation has detected an attempt
to destroy the object referenced by mutex while it
is locked or referenced.
EINVAL The value specified by mutex is invalid.
pthread_mutex_lock() 0 = successful
EINVAL The value specified by mutex does not refer
to an initialized mutex object.
EDEADLK The current thread already owns the
mutex.
pthread_mutex_
trylock()
0 = successful
EBUSY The mutex could not be acquired because it
was already locked.
EINVAL The value specified by mutex does not
refer to an initialized mutex object.
pthread_mutex_unlock() 0 = successful
EINVAL The value specified by mutex does not
refer to an initialized mutex object.
EPERM The current thread does not own the mutex.
pthread_once() None.
Table E-4. Thread Functions With Changes to Return Values Only (page 2 of 2)
Function Return Values in Standard POSIX Threads