J06.13 Release Version Update Compendium
2 Operating System
New TACL Parameter Allows You to Bind a Portmapper Process to a Single
Subnet
This RVU introduces a new TACL parameter, PORTMAPˆBINDˆIP, which allows you to bind a
portmapper process to a single subnet. To bind the process to a single subnet instead of the default,
INADDR_ANY, set the TACL PORTMAPˆBINDˆIP parameter to an IP address before you start the
portmapper process. The IP address must be an IPv4 address in dotted-decimal format. For example,
to bind the portmapper to IP address 192.168.10.10, enter this TACL command before you start
the portmapper process:
PARAM PORTMAPˆBINDˆIP 192.168.10.10
For more information about the portmapper process, see the portmap(8) reference page, either
online or in the Open System Services Shell and Utilities Reference Manual.
Migration Considerations
None.
Fallback Considerations
None.
64-Bit Support in OSS and Guardian
The HP NonStop J06.13 RVU offers several features to enable the full power of 64-bit computing.
This RVU also includes the native C/C++ compilers, linker, and debuggers to help you transition
from 32-bit applications to 64-bit OSS applications.
NonStop TNS/E systems running J06.13 or later H-series RVUs support the following new features:
• Creation of 64-bit Open System Services processes
• Access to 64-bit memory from these processes:
64-bit OSS processes◦
◦ 32-bit OSS processes
◦ Native Guardian processes
For more information about 64-bit support in OSS and Guardian, see the Open System Services
Programmer’s Guide in the NonStop Technical Library.
Migration Considerations
None. Existing 32-bit applications can coexist with 64-bit applications and run on the same
processor without modification.
Fallback Considerations
If no new 64-bit features were used after migrating from a preceding release to J06.13, there will
be no fallback impact and no application changes are required.
If 64-bit features were used in J06.13 and then a fallback to a preceding release occurs, one of
the following is required:
• Applications that were built using the LP64 data model must be rebuilt using the ILP32 data
model.
• The previous 32-bit binaries must be used.
New TACL Parameter Allows You to Bind a Portmapper Process to a Single Subnet 9