HP-UX 11i December 2003 Release Notes

Programming
Miscellaneous
Chapter 15
295
Under these circumstances, one of the following types of error messages will be issued if
you attempt to link the objects created using the HP-UX 11i compiler on an original 11.0
system.
•If you compile with +O3 or +O4you will receive the following message and a stack
trace: report error(13-12299-434) to your nearest HP service
representative(8911).
• If you compile with +O2 +I you will receive the following message and a stack trace:
Backend Assert ** Ucode versions earlier than v.4 no longer
supported(5172).
NOTE This code is not backward-compatible with the 11.0 release. Instrumented object files
cannot be moved backward.
HP DCE/9000
new at 11i
original release
HP Distributed Computing Environment (HP DCE/9000) Version 1.8 provides a
high-quality, comprehensive, standards-based framework to develop, administer, and
use distributed applications.
Kernel threads application development is now supported on HP-UX. The 32-bit version
of the kernel threads DCE library (libdcekt) is now part of the HP-UX base operating
system. The 64-bit version of libdcekt is also included.
NOTE While the DCE library (libdcekt) has been ported to 64-bit, the binaries and daemons
that are part of the DCE products are still 32-bit.
The distinction between the International and US/Canada version of DCE components
has been removed. That is, the 56-bit Data Encryption Standard (DES) which was
earlier restricted to US/Canada is now available for all customers. This means there will
only be one version of the DCE library and dced daemon, which is based on the 56-bit
DES version.
NOTE The number of LAN interfaces supported by DCED is limited to 32 and the LAN
interfaces supported by CDS is 12. If there are more than 32 LAN interfaces, the
environment variable RPC_SUPPORTED_NETADDRS can be used to identify the list of 32
LAN interfaces that are used by the Remote Procedure Call (RPC) application.
Listed below are new environment variables that have been added to support RPC
operations and to enable better usability:
• RPC_PREFERRED_PROTSEQ: This variable is used to set the preferred protocol
sequence.
• RPC_SUPPORTED_PROTSEQS: This variable helps in restricting the protocol sequence.
For example, setting this variable to ncacn_ip_tcp will enable only
connection-oriented communication.