This section describes OSF DCE and HP DCE features that will
not be supported in future releases of HP DCE.
Network Computing System (NCS) Version 1.5.1 compatibility
will not be supported in the next release
of HP DCE:
You should also be aware of likely migration to the POSIX
1003.1c standard for threads.
The rest of this section describes the NCS compatibility and
likely changes to support POSIX 1003.1c threads.
NCS 1.5.1 Compatibility |
 |
Network Computing System (NCS) Version 1.5.1 applications
are compatible with this release. The DCE Remote Procedure Call
daemon (dced) incorporates the NCS Local
Location Broker daemon support (formerly provided by llbd
or rpcd) that NCS 1.5.1 applications require.
Because neither the llbd or rpcd
daemon can coexist with dced in a cell, the
DCE cell configuration tools stop llbd or
rpcd and run dced
in its place.
Users of NCS-based software (such as NetLS, Omniback, HP MPower,
and SharedPrint/UX) should see the section entitled "Note
for Users of NCS-based Software" in Chapter 5 for important
HP DCE/9000 configuration information.
Future Support for POSIX 1003.1c Threads |
 |
The Threads API in HP DCE is likely to migrate eventually
from Draft 4 of the POSIX threads standard to the final, ratified
1003.1c standard. This migration will result in source incompatibility,
and it is recommended that application developers plan now for this
transition. HP plans to preserve binary compatibility and to provide
tools to assist in source code migration. However, developers can
prepare for this change as follows:
Isolate new threads API usage
to macros or wrapper APIs.
Minimize the use of signals and use only POSIX semantics
when programming with signals.
For example, we recommend that threaded applications use only
the functions sigaction(), sigprocmask(),
and sigwait().