J06.16 Software Installation and Upgrade Guide

KMS.SWAPFILE = 1 $SYSTEM.ZSYSSWAP.SWAP01
KMS.SWAPFILE = 2 $SYSTEM.ZSYSSWAP.SWAP02
KMS.SWAPFILE = 3 $SYSTEM.ZSYSSWAP.SWAP03
2. Issue the STATUS SWAPFILE * command to display the peak pages reserved so that you
can compare that information to the total amount of swap space available.
$SYSTEM TOOLS 50> nskcom STATUS SWAPFILE *
NSKCOM - T5838H01 BASE (01OCT07) - Jun 17 2008
Copyright 1995 Compaq Computer Corporation
$SYSTEM.SYSTEM.ZSYSCFG
KMS.SWAPFILE = 0 $SYSTEM.ZSYSSWAP.SWAP00
KMS.SWAPFILE = 1 $SYSTEM.ZSYSSWAP.SWAP01
KMS.SWAPFILE = 2 $SYSTEM.ZSYSSWAP.SWAP02
KMS.SWAPFILE = 3 $SYSTEM.ZSYSSWAP.SWAP03
Status of $SYSTEM.ZSYSSWAP.SWAP00
CPU 0
CPU Pages: Total 102305* Reserved 14936 Available 87369
Peak CPU Pages ever reserved 101855
Threshold 86959 CPU pages
* Default swapfile extents may not be fully allocated.
Status of $SYSTEM.ZSYSSWAP.SWAP01
CPU 1
CPU Pages: Total 102305* Reserved 12213 Available 90092
Peak CPU Pages ever reserved 15239
Threshold 86959 CPU pages
* Default swapfile extents may not be fully allocated.
Status of $SYSTEM.ZSYSSWAP.SWAP02
CPU 2
CPU Pages: Total 102305* Reserved 6361 Available 95944
Peak CPU Pages ever reserved 7280
Threshold 86959 CPU pages
* Default swapfile extents may not be fully allocated.
Status of $SYSTEM.ZSYSSWAP.SWAP03
CPU 3
CPU Pages: Total 102305* Reserved 5242 Available 97063
Peak CPU Pages ever reserved 6863
Threshold 86959 CPU pages
* Default swapfile extents may not be fully allocated..
Install Node Interoperability SPRs
Node interoperability is the ability of the nodes (systems) in an Expand network to communicate
and interact with each other. An Expand network can be interconnected using various technologies
such as Expand over IP and ServerNet Cluster. See the NonStop Networking Overview for more
information about and diagrams of NonStop platform interoperability.
In addition to interoperability issues for nodes connected through Expand, there are software
migration and software management issues to consider, such as accelerating TNS object files on
a system running an RVU series for posterior use in a system running another RVU series, DSM/SCM
software management in an environment composed of systems running different RVU series, and
moving objects built on a system running an RVU series to a system running another RVU series
by means of Expand, FTP, or media such as magnetic tapes.
NOTE: This manual does not list the SPRs needed for BladeCluster Solution interoperability. For
specific SPRs required for the BladeCluster Solution, see the BladeCluster Solution Manual.
Install Node Interoperability SPRs 55