Kernel-Managed Swap Facility (KMSF) Manual

NSKCOM Command Reference
Kernel-Managed Swap Facility (KMSF) Manual425824-005
4-12
COMMENT Command
COMMENT Command
The COMMENT, or “==” command causes the rest of the line to be treated as a
comment and ignored by NSKCOM.
If you use the NSKCOM LOG command to log your NSKCOM session, this command
is a useful tool for commenting your changes.
text
is the information that you enter at the keyboard.
The following examples show two ways in which you might use the COMMENT
command to comment on your actions:
NSK-== Add a second swap file for CPU 1
NSK-COMMENT Add a second swap file for CPU 1
DEL[ETE] Command
The DELETE command deletes a swap file that is not in use or that marks an in-use
swap file for future deletion. Issuing the DELETE command for a swap file does not
affect existing processes with space reservations in the swap file. Existing processes
using the file continue to run and can increase their current reservations in the swap
file up to the allocated size of the file. (Default swap files are allowed to grow up to their
file size.) The DELETE command prevents any new reservations to be given out for
the file.
This command can be issued only by super-group users (255, n).
filename
is the name of the swap file to be deleted. The variable filename is specified as:
$volume.subvolume.filename.
If a swap file is in use, issue the STOP command before the DELETE command. If the
file is in use when you enter the DELETE command, it is marked for future deletion.
When all processes using the file have terminated and a super-group user (255, n)
runs NSKCOM, NSKCOM deletes the file from disk.
As shown in Example 4-7 on page 4-13, use of a file is first stopped, and then, when
use of the file has stopped completely, the file is deleted. Each cleaned extent is
COMMENT [text] | == [text]
DEL[ETE] SWAPF[ILE] filename
Note. If the target swap file is the only swap file open, NSKCOM responds with the error
“Cannot delete a CPUs last open swapfile!” and does not delete the file.