AIX Version 4.3 Differences Guide

mlockall()
mq_getattr()
mq_open()
mq_send()
mq_unlink()
munlockall()
sched_get_priority_max()
sched_getparam()
sched_rr_get_interval()
sched_setscheduler()
sem_close()
sem_getvalue()
sem_open()
sem_trywait()
sem_wait()
shm_unlink()
sigtimedwait()
timer_create()
timer_getoverrun()
mq_close()
mq_notify()
mq_receive()
mq_settattr()
munlock()
nanosleep()
sched_get_priority_min()
sched_getsceduler()
sched_setparam()
sched_yield()
sem_destroy()
sem_init()
sem_post()
sem_unlink()
shm_open() function
sigqueue()
sigwaitinfo()
timer_delete()
timer_gettime()
timer_settime()
4.2.2 Unsupported Threads Options
AIX 4.3.2 does not support the optional pthread interfaces provided in Table 17.
Table 17. Unsupported Optional Threads Interfaces
pthread_attr_getinheritsched()
pthread_attr_setinheritsched()
pthread_mutex_getprioceiling()
pthread_mutex_setprioceiling()
4.2.3 Dynamic Linking Extension
The dynamic linking extension that came out of the Aspen group comprises a set
of four routines and a header file to provide a portable API for manipulation of an
implementation-defined class of files, such as shared libraries. These routines
are based on those introduced in UNIX System V Release 4.
Use of dynamic linking allows several benefits for application developers:
• The ability to share commonly-used code across many applications, leading to
disk and memory savings.
• It allows the implementation of services to be hidden from applications.
• It allows the re-implementation of services. For example, to permit bug and
performance fixes or to allow multiple implementations selectable at runtime.
68 AIX Version 4.3 Differences Guide