HP NonStop G-Series - Manual (Page 171)

Performing Routine Disk Operations
Guardian User’s Guide — 425266-001
9- 25
Using NSKCOM to Monitor and Alter Swap Files
KMSF and Operations
KMSF affects installation and configuration. For kernel-managed swap files, system
administrators must plan for and configure:
•
How much swap space is needed
•
Where to place swap files
•
What guidelines they need to create for operations staff on monitoring and altering
swap files
KMSF also affects routine operations. Operations staff should monitor KMSF and
operator messages to spot potential problems and dynamically add swap space as
needed. Event Management Service (EMS) messages are generated to alert staff to swap
files that have reached a configured threshold and to changes in KMSF configuration.
KMSF does not use more disk space than conventional swap files because the size and
number of temporary files that were formerly used for swapping decline as usage of
KMSF increases.
KMSF and Applications
Under KMSF, the memory needs of processes, including the main stack, globals, heap
space, extended data segments, and shared run-time library (SRL) instance data, are
copied to a common swap file or files managed by the NonStop™ Kernel.
You do not need to recode applications for KMSF.
Using NSKCOM to Monitor and Alter Swap Files
Use the NSKCOM utility of KMSF to monitor your kernel-managed swap files to
ensure that you have adequate swap space available. If adequate swap space is not
available, it might prevent process creation and cause processes to fail. You can also use
NSKCOM to configure and manage swap files if you need to make any changes.
Monitoring Swap Files
To monitor kernel-managed swap files, you can use NSKCOM to review the status of
the swap files and the swap file statistics for each processor.
1. Run NSKCOM.
> NSKCOM