Kernel-Managed Swap Facility (KMSF) Manual

Configuring KMSF

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

2-6

Making Adjustments to Your Configuration

File size 16.000 GB

Format 2

Threshold Default

The ASSUME LIKE command sets the attribute values for all subsequent NSKCOM

commands to be like those specified in the file $SWAP.KERSWAP.CPU00A. The

RESET command resets the assumed defaults back to the original values (see the

RESET command on page 4-22).

The files you added are displayed in the opening banner the next time you run

NSKCOM (Example 2-2).

Making Adjustments to Your Configuration

Once you have installed and configured KMSF initially, you might want to alter your

configuration. For example:

•

If a swap file for a particular processor is running low on free space, you might

want to add extents to the existing file or add a new swap file.

•

You might want to stop using or delete a file to prevent the file from growing, to

force swap activity to other swap files, or to prepare for bringing down a disk.

You use the NSKCOM STOP command to stop use of a file by additional

processes and the DELETE command to mark a file for deletion when its current

processes have terminated. NSKCOM shows these files as marked STOP, STOP

PENDING, DELETE, or DELETE PENDING.

The DELETE and STOP attributes are persistent across system loads and

processor reloads. If a processor is loaded or reloaded, KMSF does not use a file

that is marked STOP or DELETE. If no configured swap file is available, KMSF

attempts to create a default swap file.

For information about altering your configuration, see Section 3, Managing KMS Files

and Section 4, NSKCOM Command Reference.

Example 2-2. Running NSKCOM When Swap Files Are Configured

$SYSTEM SYS42 4> NSKCOM

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

$SYSTEM.SYSTEM.ZSYSCFG

KMS.SWAPFILE = 0 $SWAP.KERSWAP.CPU00A

KMS.SWAPFILE = 1 $SWAP.KERSWAP.CPU01A

KMS.SWAPFILE = 2 $SWAP.KERSWAP.CPU02A

KMS.SWAPFILE = 3 $SWAP.KERSWAP.CPU03A

NSK-