Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Configuring a Workgroup
Compatibility Between HP-UX Releases 10.x and 11.x
Chapter 4452
It is advantageous to run your software without porting to 11.0 when:
• You want to simplify the transition process.
• You want to use a single executable for both HP-UX 10.x and HP-UX
11.0.
• Your software is not a library. (Native versions of libraries are
usually needed for optimal performance.)
• You do not need to recompile your software with the new ANSI C++
compiler.
• Your software does not use sigcontext, which is machine-dependent
and thus not portable.
When to Port Software to HP-UX 11.0
Porting your software and recompiling involves effort, since you make
source changes and recompile on HP-UX 11.0.
Moving your software source to the 11.0 release of HP-UX is useful for
several reasons: to take advantage of new features such as 64-bit
capability, to adhere to industry standards, and to reduce maintenance
costs. The Software Transition Kit (STK) is designed to help application
or library developers who need to transition software from HP-UX 10.x
to HP-UX 11.0. The documents and tools in the STK will simplify the
transition process. Refer to “What STK Transition Tools are Available?”
on page 453 for more information.
You should port your software if any of the following conditions are true:
• You need a 64-bit binary.
• Your primary concern is running your software on HP-UX 11.0 with
optimal performance.
• You do not need a single binary for both HP-UX 10.x and 11.0.
• Your software is a library. Since HP-UX 11.0 applications can only
link with HP-UX 11.0 libraries of the same word size, you must
provide both a 32-bit and 64-bit HP-UX 11.0 version of your library.
• You need to recompile your software with the new ANSI C++
compiler.
• Your software uses sigcontext, which is machine-dependent and
not portable.