NonStop Operating System Event Management Programming Manual

NonStop Operating System Event Messages (ZNSK)
HP NonStop Operating System Event Management Programming Manual520372-020
13-39
Messages
Recovery. If other swap files are available for the processor, no corrective action is
needed.
If no other swap files are available for the processor, you must add and enable a swap
file for that processor to allow for process creation. Because you cannot start a new
process on that processor while no swap file is enabled, you can run NSKCOM on
another processor. Use the NSKCOM ADD and NSKCOM START commands to add
and enable a swap file for the processor. You can also use the NSKCOM START
command to put the stop-pending file back into use.
209: ZNSK-EVT-KMS-SWAP-PURG-PENDING
The indicated KMSF swap file has been marked for deletion.
Unconditional Tokens
Cause. An NSKCOM DELETE command specified the indicated swap file.
Effect. The swap file is marked for deletion in the configuration file ZSYSCFG. When
all processes that are using the marked swap file have terminated, the swap file is
deleted.
Recovery. This is an informational message only; no corrective action is needed. You
can cancel the pending deletion by entering an NSKCOM START command.
Subject: ZNSK-TKN-FILE
Potentially critical event: No
Action event: No
Message sender: NSKCOM process
TMDS collector: No
OSM/TSM collector: No
Unconditional Tokens
ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT
ZNSK-TKN-FILE token-type ZSPI-TYP-STRING
ZNSK-TKN-CPU token-type ZSPI-TYP-INT
Event-Message Text
KMSF SWAPFILE PURGE PENDING: swapfile CPU cpu
Token Description
ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSK-EVT-KMS-
SWAP-PURG-PENDING (209).
ZNSK-TKN-FILE Subject token that specifies the name of the swap file that
was marked for deletion.
ZNSK-TKN-CPU Processor number of the processor associated with the
indicated swap file.