H06.12 Software Installation and Upgrade Guide

Safeguard Logon Without a Password
Starting in the H06.11 RVU, is enhanced to allow users to logon without a password. (This
capability can be used only if the SUPER.SUPER user has granted the program file that permission
through Safeguard.)
Migration
There are no migration or fallback considerations specific to the new logon feature. However,
you can use the mitigation procedure described under “Migration in a Safeguard Environment”
(page 54) to handle any unexpected failures that might occur when migrating to the new version
of Safeguard.
For more information, see Chapter 10 of the Safeguard Administrator's Manual.
OSI FTAM and MHS Longer Password Support
Starting with the H06.10 RVU, the OSI FTAM (T6982) and MHS (T7937) products support
passwords up to 64 bytes long. The passwords can also include special characters. To use these
features, the Standard Security T6533H04 SPR or later must be installed.
Compiler Default Change for Object Code Generation
Prior to the H06.08 RVU, the native C/C++, COBOL, and pTAL compilers generated preemptable
object code by default. Beginning in H06.08, the compilers generate non-preemptable object code
by default. Non-preemptable object code is more efficient than preemptable object code and
results in faster compilation and execution. Preemptable object code is required only when
building DLLs that provide preemptable symbols. The H06.08 versions of the compilers provide
a command line option to specify to specify whether or not preemptable object code is generated.
Option NameCompiler NameCompiler Host
GLOBALIZEDCCOMP, CPPCOMP, ECOBOL,
EPTAL
TNS/E Guardian
-Wglobalizedc89, ecobolTNS/E OSS and Windows
-globalizedeptalWindows
Because of the performance implications, developers should specify the option to generate
preemptable object only when building DLLs that provide preemptable symbols.
Default Floating-Point Type Change
Beginning in the H-series RVUs, the default floating-point format used by the C/C++ compiler
is changed. In G-series, the default is Tandem floating-point format; on H-Series, the default
IEEE format. The two formats are incompatible; an application must consist of either all Tandem
format modules or all IEEE format modules. Certain HP-supplied libraries use the default IEEE
format. If user programs also use the default format, there is no problem. However, any user
program that explicitly specifies the option to use the Tandem format will encounter a linker
error when attempting to load an HP module that uses IEEE format. The recommended
workaround is to compile applications using IEEE format.
Providers of DLLs should also be aware of this default change, and take steps to provide libraries
that are compatible with both floating-point formats. This can be accomplished in the following
ways:
• Write the library to be floating point neutral
• Provide two versions of the library, one in Tandem format and one in IEEE format.
58 H06.12 Installation, Migration, and Fallback Considerations