H06.03 Release Version Update Compendium

H06.03 Overview
H06.03 Release Version Update Compendium—540008-002
1-3
Application Differences Between the H-Series and
G-Series RVUs
•
SIT Load and Tape Dump and not supported in the OSM Low-Level Link for
H-series. Integrity NonStop NS-series processors must be loaded from disk, and
processor dumps can be configured in HP Tandem Failure Data System (TFDS) or
taken manually through TACL commands.
•
The OSM Low-Level Link is updated to add a new System Load dialog box
specifically for H-series. You can save up to four alternate system load
configurations in the OSM Service Connection by using the Save as System Load
Configuration action on SCSI and Fibre Channel disks.
•
Both NonStop S-series and Integrity NonStop NS-series servers have the ability to
continue to operate from a power source for some time after the main system
power has been removed. In NonStop S-series systems, this power source
consists of batteries internal to the enclosure, while in the more modular Integrity
NonStop NS-series systems, it consists of a UPS to which various components are
connected.
The actual time the operating system can wait before shutdown is calculated at the
time of the power failure. In NonStop S-series systems, the operating system uses
the smaller of the calculated time value and the POWERFAIL_DELAY_TIME value
to determine how long it waits before starting to shut down system operations. In
Integrity NonStop NS-series systems, the operating system uses the value that the
operator specifies as the POWERFAIL_DELAY_TIME value.
For Integrity NonStop NS-series systems, you can specify the key word
RIDETHRUONLY as a value for this attribute. RIDETHRUONLY allows the
operating system to wait indefinitely.
Application Differences Between the H-Series
and G-Series RVUs
Differences between H-series and G-series RVUs are due mainly to architectural
differences between TNS/R and TNS/E hardware platforms. The Integrity NonStop
NS-series system uses a different instruction set at the hardware level. Therefore, new
compilers and tools have been designed to create application code files that execute
on the TNS/E platform.
Differences in the G-series and H-series development environments include:
•
TNS/R native object files cannot be executed on a TNS/E platform. All TNS/R
native programs must be recompiled using a TNS/E native compiler.
•
TNS/E native object files cannot be executed on a TNS/R platform.
•
The H-series OSS environment does not support TNS execution. OSS programs
must be migrated to TNS/E native mode to run on an H-series system.
•
TNS/E native development tools (compilers, linkers, utilities) have new names,
although their functionality is nearly identical.