Kernel-Managed Swap Facility (KMSF) Manual

Managing KMS Files

Kernel-Managed Swap Facility (KMSF) Manual—425824-005

3-3

Using NSKCOM to Monitor KMS Space

NSKCOM Security

You must be a super-group user (255, n) in order to change the KMSF configuration by

adding, altering, stopping, or deleting swap space. Only one super-group user at a time

can use NSKCOM to change the configuration. When a super-group user issues a

command that changes the configuration, the user obtains a lock on the file

$SYSTEM.SYSTEM.KMSFLOCK. The user maintains the lock until exiting NSKCOM.

While a user has the lock, other super-group users are limited to informational

commands. If a super-group user enters a command that would change the KMSF

configuration while the lock is held by another user, the user receives the following

error message:

*** Warning: ZSYSCFG is locked by another user:

HP recommends the files $SYSTEM.SYSTEM.KMSFLOCK and

$SYSTEM.SYSTEM.ZSYSCFG be secured “NGNG” so that super-group users (255,n)

can update them. The KMSF swap files in the system must be owned by super

(255,255) and secured “OGOG.”

Figure 3-1. NSKCOM Opening Banner

Usage threshold at which an EMS

message is generated. If blank, the file has

a default threshold of 85 percent.

$SYSTEM SYS66 35> NSKCOM

NSKCOM - T5838H01 BASE (01OCT04) - Apr 15 2005

$SYSTEM.SYSTEM.ZSYSCFG

KMS.SWAPFILE = 0 $SWAP.KERSWAP.CPU00A THRESHOLD 70

KMS.SWAPFILE = 1 $SWAP.KERSWAP.CPU01A

KMS.SWAPFILE = 0 $SWAP.KERSWAP.CPU00B

KMS.SWAPFILE = 1 $SWAP.KERSWAP.CPU01B

KMS.SWAPFILE = 2 $SWAP.KERSWAP.CPU02A

KMS.SWAPFILE = 3 $SWAP.KERSWAP.CPU03A

NSK-

NSKCOM

version

Configuration

file

List of

configured

swap files

NSKCOM prompt

Processor

(CPU)

Swap file serving the

specified processor

VST005.vsd