Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX 11i Version 2 May 2005 Release Notes: HP 9000 Servers, HP Integrity Servers, and HP Workstations > Chapter 2 Introduction to HP-UX 11i Version 2

HP-UX 11i v2 Compatibility

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

HP-UX Compatibility between HP-UX Releases, Across Architectures, and Across Hardware Platforms

Introduction

HP understands the need for investment protection better than any other computer vendor. HP provides complete compatibility for the most comprehensive investment protection in the industry. HP provides:

  • Binary and source code compatibility across operating system releases

  • Binary and source code compatibility across architectures

  • Field upgradability across architectures (HP customers can upgrade their systems in place)

  • Binary compatibility across hardware platforms including PA-8800 binary compatibility

Compatibility across Operating System Releases

HP provides forward binary compatibility between the versions of HP-UX 11i on the same architecture. This means that:

  • HP-UX 11i v1.5 applications run unmodified on HP-UX 11i v1.6 and on HP-UX 11i v2.

  • HP-UX 11i v1.6 applications run unmodified on HP-UX 11i v2.

  • HP-UX 11i v2 September 2004 and later releases are engineered to provide application binary compatibility between HP-UX 11i v1 (B.11.11) and earlier releases of HP-UX 11i v2.

This binary compatibility does not apply to kernel-intrusive applications or applications that rely on proprietary data structures inside HP-UX.

NOTE: HP-UX 11i v2 returns B.11.23 as the release identifier in the uname command.

HP C compilers for the HP 9000 (PA-RISC) systems support the C89 (ISO/IEC 9899:1989) standard. The C compilers for HP Integrity (Itanium®-based) systems support both the C89 and newer C99 (ISO/IEC 9899:1999) standards. This means that while C code developed on HP 9000 servers is forward compatible to HP Integrity servers, the reverse is not necessarily true.

HP-UX 11.0 applications that have been certified or proven to run well on HP-UX 11i v1 can also be considered to be compatible with HP-UX 11i v2. (HP-UX 11.0 application programs can run unmodified on HP-UX 11i v1 although binary compatibility is not guaranteed for applications that are kernel intrusive or depend on internal proprietary data structures of HP-UX 11i v1.) Compatibility details are fully documented in these Release Notes. Additionally, there is complete data compatibility between the architectures.

Compatibility between HP-UX 11i for HP 9000 (PA-RISC) systems and HP-UX 11i for HP Integrity (Itanium®-based) systems includes the following features:

  • HP-UX 11i v2 for Itanium®-based systems can transparently execute PA-RISC binaries. This is possible through the Aries dynamic code translation technology which is a built-in, integrated part of every copy of HP-UX 11i for Itanium®-based systems. Performance in compatibility mode is likely to be less than native mode, but binary compatibility ensures that all PA-RISC applications can execute on the Itanium®-based architecture without recompilation.

  • HP-UX 11i v2 for Itanium®-based systems and HP-UX 11i v2 for PA-RISC systems are built from the same source code. This means that HP-UX 11i v2 has the same look and feel and operates in a very similar fashion on both architectures.

  • The system management, security, and high availability tools and products for HP-UX 11i v2 for HP Integrity systems are the same as for HP-UX 11i v2 for HP 9000 systems. This means that current HP-UX 11i system administrators can apply their skillsets directly to HP-UX 11i for HP Integrity systems.

  • HP-UX 11i v2 features application source code compatibility between the HP 9000 and HP Integrity systems. Application programs from HP-UX 11i for HP 9000 systems can be made into native applications on HP Integrity systems with no source code modifications necessary. (HP-UX 11i for Itanium®-based systems supports both 32-bit and 64-bit applications even though Intel® Itanium® is a 64-bit architecture.) However, converting a 32-bit application into a 64-bit application may require some source code changes.

  • HP-UX 11i for Itanium®-based systems has the same data formats as HP-UX 11i for PA-RISC systems. This means that there is complete data interoperability between the two architectures. This interoperability allows the seamless integration of HP-UX 11i v2 systems into an existing network of HP-UX systems.

Upgradability across Architectures

As of July of 2002 HP began to introduce HP-UX 11i servers that support both PA-RISC and Intel® Itanium® processors. For these servers, customers are be able to specify the architecture they desire when they order systems. Servers that are initially ordered as PA-RISC servers can be field-upgraded to Itanium®-based systems and will enjoy all of the compatibility advantages listed above.

Independent Software Vendor (ISV) Compatibility across Architectures

With the source, data, and binary compatibility that HP provides from the PA-RISC architecture to the Itanium®-based architecture, it is expected that the vast majority of independent software vendors (ISVs) that support applications on PA-RISC will transition these applications to HP-UX 11i for Itanium®-based systems. 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/Itanium®-based 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 Itanium®-based systems. The following list documents the exceptions to binary compatibility. HP's Aries dynamic code translator does not support the following:

  • Mixing binaries between PA-RISC and Intel® Itanium ®. An 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.

  • Signaling via floating point Not a Numbers (NaNs).

  • Applications or debuggers that use ptrace, ttrace, and profil system calls.

  • Core dumps for PA-RISC applications that abort.

  • Automatic synchronization of data and instruction caches for applications that dynamically generate code such as Java.

  • Applications that read the B-bit in the Process Status Word (PSW).

  • Applications that use maximum virtual memory (because the dynamic translator itself consumes a small amount of the virtual memory of a process).

  • Applications that rely on differences between vfork and fork system calls.

  • The emulation of debugging tools that have architectural dependencies on the PA-RISC architecture.

Recompiling 32-Bit PA-RISC Applications for Native Execution on Itanium®-based systems

In nearly all cases, 32-bit PA-RISC applications can be recompiled for native execution on Itanium®-based systems without source code modifications. This is true because the HP compilers for Intel® Itanium® support both 32-bit and 64-bit data models.

In the case of a 32-bit PA-RISC application that is being recompiled for native execution on Itanium®-based systems, the compiler will emit instructions that cause the application to behave as though it is a 32-bit application executing on a 32-bit architecture even though the underlying architecture is 64 bits. This is transparent to the application; it has no awareness that it is actually executing on a 64-bit architecture.

It is this feature of the HP compilers that allows the vast majority of 32-bit PA-RISC applications to be recompiled without source code modification for native execution on the Intel® Itanium® architecture.

Help for Independent Software Vendors (ISVs) Moving to HP-UX 11i v2

Independent Software Vendors (ISVs) whose HP-UX 11i v1 application meets the criteria for binary compatibility (i.e., not kernel intrusive, etc.) and fails to function on HP-UX 11i v2 for HP 9000 as it functions on HP-UX v1, can contact HP through a special support line (for North America) at 1-800-249-3294 and use option 2, and then option 1. Help is also available alternatively by sending an e-mail to spp@cup.hp.com. When calling this number or sending an e-mail, identify the problem as a compatibility failure and the support staff will help you with the situation.

Binary Compatibility Across Hardware Platforms

HP maintains application binary compatibility across all hardware platforms of the same family which are supported by the same version of HP-UX. In other words, binary compatibility across the members of a hardware family (such as PA-RISC) is provided if the following conditions apply:

  • The hardware platforms are members of the same family (that is, they are all PA-RISC-based or they are all Itanium®-based).

  • The application software is run on the same or a later version of HP-UX. (Binaries are not necessarily backward-compatible; that is, a software application may not run properly on an earlier version of HP-UX.)

  • The application software has used only externally documented and supported software interfaces (that is, it does not use undocumented interfaces).

  • The application software has no dependencies on specific types of hardware (for example, specific mass storage devices or specific I/O or networking adapters).

HP has an excellent record of introducing new processors that provide complete software binary compatibility with previous processors, thus protecting customer and partner investments and allowing support for new processors with a minimum of risk and investment. HP has always recognized that software binary compatibility with new processors is an important partner and customer requirement.

PA-8800 Binary Compatibility

Applications and software developed for systems with the PA-8X00 processors will run correctly without modification on PA-8800 modules. These new processors differ from previous ones in the use of a dual-core module that replaces a single PA-8700 processor, thus doubling the number of processors that each server can support and improving price/performance. PA-8800 modules are seen by HP-UX as two separate processors and are supported by HP-UX 11i v2 September 2004 and later release.

Compatibility Issues or Exceptions in HP-UX 11i v2 May 2005

Compatibility issues or exceptions have been noted for the following products or features that have been updated in May 2005. For details, see the indicated pages.

For documentation of compatibility issues or exceptions in previous updates to HP-UX 11i v2, see the previous editions of the HP-UX 11i v2 Release Notes, available at http://docs.hp.com/en/oshpux11iv2.html. The HP-UX 11i v2 September 2004 Release Notes, in particular, lists compatibility exceptions from HP-UX 11i v1 to HP-UX 11i v2.

NOTE: Please note that your system must have an HP-UX 11i v2 Operating Environment (OE) from September 2004 (or later) before updating your system with any individual patches, patch bundles, or products released from September 2004 forward.

Chapter 4: Workstation- and Server-Specific Information. 

Chapter 5: General System Administration. 

Chapter 6: Disk and File Management. 

  • No issues at this time.

Chapter 7: Internet and Networking. 

  • No issues at this time.

Chapter 8: Security. 

Chapter 9: Commands and System Calls. 

  • No issues at this time.

Chapter 10: Libraries and Programming. 

Chapter 11: Internationalization. 

  • No issues at this time.

Chapter 12: Other Functionality. 

  • No issues at this time.

Support of Products

For information about the support of products not listed in elsewhere in this document, refer to the product’s individual documentation, which may be found at the following locations:

See also “Software Transition Kit”, for information about a collection of tools and documents to help transition applications from various operating systems, such as Tru64 UNIX or Sun Microsystems Solaris, or from earlier versions of HP-UX.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2005 Hewlett-Packard Development Company, L.P.