HP-UX 11i Version 2 June 2006 Release Notes

Introduction to HP-UX 11i Version 2
HP-UX 11i v2 Compatibility
Chapter 2
30
(HP-UX 11i on Integrity servers supports both 32-bit and 64-bit applications
even though Integrity servers are a 64-bit architecture.) However, converting a
32-bit PA-RISC application into a 64-bit Integrity server application may require
some source code changes.
— Application Build Environment Compatibility:
HP-UX 11i also features Application Build Environment compatibility across the
PA-RISC and Integrity server architectures. This means that PA-RISC
application build environments (make files, script files, etc.) can be moved to
Integrity servers and will, without modification, function the same way that they
did on PA-RISC.
• HP-UX 11i on Integrity servers has the same data formats as HP-UX 11i on PA-
RISC. This means that there is complete data compatibility between the two
architectures. This interoperability allows the seamless integration of HP-UX 11i
Integrity servers into a network of HP-UX 11i PA-RISC systems.
HP Integrity Virtual Machines Compatibility
HP Integrity Virtual Machines (VM) are engineered to provide application binary
compatibility between HP-UX 11i v2 Integrity server native applications and the same
applications running in virtual machines. This binary compatibility applies to
applications with no specific device dependencies and to applications that depend only
on devices currently virtualized by Integrity VM. Most applications do not have specific
device dependencies. However, if your application has specific device dependencies,
please refer to the “HP Integrity Virtual Machines QuickSpec” at http://docs.hp.com
for details.
ISV Application Availability Across Architectures
With the source, data, and binary compatibility that HP provides from the PA-RISC
architecture to the Integrity server architecture, it is expected that the vast majority of
independent software vendors (ISVs) that support applications on PA-RISC will be able
to readily transition these applications to HP-UX 11i on Integrity servers. This means
that not only will HP-UX 11i and its layered system management, security, and high
availability products have a common “look and feel” on the two architectures, it also
means that application products will have a common “look and feel” across the two
architectures, thus eliminating the need to retrain users for new applications.
Exceptions to PA-RISC/Integrity server Binary Compatibility
In nearly all cases PA-RISC applications can execute under the Aries dynamic code
translator which is included as an integrated component in every copy of HP-UX 11i for
Integrity servers. The following list documents the exceptions to binary compatibility.
HP's Aries dynamic code translator does not support the following:
• binary mixed mode between PA-RISC and Integrity servers (application must be all
PA-RISC, all 32 bits or all 64 bits)
• applications compiled on HP-UX 8.x or earlier
• PA-RISC privileged instructions
• applications that depend on kernel data structures
• timing-dependent applications