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-11
Changed Thread Functions
pthread_mutexattr_
destroy()
0 = successful
EINVAL The value specified by attr is invalid.
pthread_mutexattr_
getkind_np()
0 = successful
-1 = error (Check errno for last error, such as EINVAL.)
pthread_mutexattr_
init()
0 = successful
EINVAL The value specified by attr is invalid.
ENOMEM Insufficient memory exists to initialize the mutex
attributes object.
pthread_mutexattr_
setkind_np()
0 = successful
-1 = error (Check errno for last error, such as EINVAL.)
pthread_mutex_init() 0 = successful
EAGAIN The system lacked the necessary resources
(other than memory) to initialize another mutex.
EINVAL The value specified by attr is invalid.
ENOMEM Insufficient memory exists to initialize the mutex.
pthread_self() The current thread ID.
pthread_
setcancelstate()
0 = successful
EINVAL The specified state is not
PTHREAD_CANCEL_ENABLE or
PTHREAD_CANCEL_DISABLE.
pthread_
setcanceltype()
0 = successful
EINVAL The specified type is not
PTHREAD_CANCEL_DEFERRED or
PTHREAD_CANCEL_ASYNCHRONOUS.
ENOTSUP An attempt was made to set the cancel type to
PTHREAD_CANCEL_ASYNCHRONOUS.
pthread_
setschedparam()
0 = successful
EINVAL The value specified by policy or one of the
scheduling parameters associated with the scheduling
policy policy is invalid.
ENOTSUP An attempt was made to set the policy or
scheduling parameters to an unsupported value.
ESRCH The value specified by thread does not refer to
an existing thread.
Table E-5. Thread Functions With Changes to Return Values Among Other
Changes (page 4 of 5)
Function Return Values in Standard POSIX Threads