HP-UX 11i Version 2 June 2007 Release Notes

Introduction to HP-UX 11i Version 2
HP-UX 11i v2 Compatibility
Chapter 2
29
Compatibility between Architecture Families
In addition to the compatibility provided within an architecture family, HP-UX 11i on
HP 9000 servers is data, source, and build environment compatible with HP-UX 11i on
Integrity servers. Build environments and source files can be moved from HP 9000
servers to Integrity servers and be rebuilt without modification.
Application binaries that were built on HP-UX on HP 9000 servers are binary
compatible, with some limitations, with HP-UX on HP Integrity servers when running
through the Aries Dynamic Code Translator. The use of Aries can be completely
transparent. For more information about Aries, see http://www.hp.com/go/aries.
Support
HP is committed to providing investment protection via compatibility as outlined above.
Any owner of application code that meets the criteria for compatibility, who has
encountered a compatibility failure as defined by this document, should contact HP
through a special support line (for North America) at 1-800-249-3294 and use option 2.
Help is also available alternatively by sending an e-mail to [e-mail]. Please
identify the problem as a “compatibility failure.”
For More Information
• http://www.hp.com/go/hpux11i
• http://www.hp.com/go/integrity
Definition of Terms and Levels of Compatibility
There are multiple types of compatibility that need to be defined:
• Forward Compatibility means that there is compatibility between a version and a
later version. It does not mean or include compatibility going from the later version
to the previous version. All references to compatibility in this document are for
forward compatibility only.
• Build environment compatibility means that application build environments
(makefiles, script files, etc.) can be moved and used unchanged from the original
system to the target system.
• Source compatibility refers to the ability to compile the same application code source
file on an original system and a compatible system with different versions of the HP
compiler.
• Binary compatibility refers to the ability to compile an application on a specific
solution (architecture, hardware platform, operating system version) to produce a
binary file. That binary file, without modification, can be run on the solution where it
was created and it can be on a target solution which is binary compatible.
• Data compatibility means that the data format on the different targets is the same.
• “Well-behaved” User Space Applications:
HP-UX provides compatibility for applications that are user space (as opposed to
kernel intrusive) applications that are “well behaved.” A “well behaved” user space
application is an application that adheres to the following characteristics: