Node and Host Name Sizes on HP-UX: Using the Expanded Capabilities of HP-UX

names generally do not get sufficiently large to cause mail IDs to exceed the original 255-

byte limit.

The sendmail utility can create files that include the host name (such as

.forward.hostname+). With longer host names, it is somewhat more likely that the path

to these files can exceed the PATH_MAX value, thus causing failures. Because the PATH_MAX

value is 1023, this should be a problem only when the directory path itself already exceeds

756 bytes. For more information, see “File Names”.

The standard BOOTP protocol supports host names up to 64 bytes (including null terminator).

The server truncates any name that is longer. Because DNS standards limit host name labels

to 64 bytes (including null terminator), this is generally not an issue when the name is not

qualified with the domain name. In cases where the label or qualified name exceeds this

limit, a shorter host-name alias might be assigned and used with the BOOTP utilities.

The rwho protocol supports host names up to 32 bytes. Longer host names cannot be

supported in rwhod(1m) and rwho(1) and should not be assigned on systems running the

rwhod system daemon.

Some utilities, such as remsh(1), internally append the domain name to the host name, if it

is not already specified, to form a full canonical name. This full name cannot exceed 255

bytes (excluding null terminator). This is not a problem as long as host names conform to the

Internet rules summarized in Appendix A “Rules in Constructing Host and Node Names”.

Java

The following table lists the minimum Java™ versions required for support of expanded node

and host names. Earlier versions do not have full support.

Optional Product Description

Bundle/Product

Name

Minimum Version

Needed for Node/Host

Name Expansion

Java 1.4.2 JDK T1456AA 1.4.2.07

Java 1.4.2 JRE T1457AA 1.4.2.07

Java 1.3.1 JDK B9788AA 1.3.1.15

Java 1.3.1 JRE B9789AA 1.3.1.15

Languages Other Than C/C++

Only the HP C and C++ compilers support the FLV mechanism used for uname() as

described in this document.. Other language compilers and linkers do not support that

mechanism. Programs written in other languages must use explicit source code sequences to

access the versioned uname() function.