NonStop NS-Series Operations Guide (H06.12+)

A Operational Differences Between Systems Running
G-Series and H-Series RVUs
Users familiar with systems running G-series RVUs will find several major differences in the
operational environment of systems running H-series RVUs. Although many of the operations
to be performed remain the same, the tools you use to execute these operations might differ
significantly. For H-series RVUs, these changes have been made:
TSM is not supported in H-series. You must use OSM. Also, OSM’s graphical representation
of modular systems has a different look in H-series.
In power failures, there is no memory hold-up for H-series. Ride-through is available only
if the customer has a site uninterruptible power supply (UPS) or an in-cabinet UPS for all
the affected cabinets.
TAPEBOOT is not supported in H-series.
In H-series, native compilers and linkers have new names. Therefore, automated scripts
might require changing.
Subvol for public libraries is SYSnn in G-series. In H-series, it is ZDLLnnn and requires
changing scripts.
REPLACEBOOT only applies to TNS and TNS/R. It does not apply to TNS/E.
On G-series servers, the OSS shell command ls displays the contents of directories without
visually distinguishing between subdirectories and files. On H-series servers, ls displays
the contents of directories with a visual distinction between subdirectories and files --
subdirectory names are suffixed with a slash (/). This difference affects any OSS shell script
that relied upon processing the output of the ls command.
For H-series, DSM/SCM installation default is Manage OSS Files. For G-series, the default
is not to manage OSS files.
KMSF swap files have a larger memory size. It is now four times memory size per processor.
Changes to automated debugging and dump mechanisms are required in H-series because
of the new debuggers and debugger commands.
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.
195