/SUSPEND[=SUPERVISOR] /SUSPEND=KERNEL /NOSUSPEND Requires privileges as described in text. Temporarily stops the process's activities. The process remains suspended until another process resumes or deletes it. Use the qualifiers /NOSUSPEND and /RESUME to resume a suspended process. Specify either of the following keywords with the /SUSPEND qualifier to produce different results: Keyword Explanation SUPERVISOR Specifies that the named process is to be suspended (default) to allow the delivery of asynchronous system traps (ASTs) at EXEC or KERNEL mode. Specifying this keyword is optional. KERNEL Specifies that the named process is to be suspended such that no ASTs can be delivered. To specify the KERNEL keyword, you must be in either KERNEL mode or EXEC mode, or have CMKRNL (change mode to kernel) and CMEXEC (change mode to executive) privilege enabled. Note that this was the default behavior of the SET PROCESS/SUSPEND command for versions of OpenVMS prior to VMS Version 5.0. Depending on the operation, the process from which you specify the /SUSPEND qualifier requires privileges. You must have GROUP privilege to suspend another process in the same group, unless that process has the same user identification code (UIC). You must have WORLD privilege to suspend any other process in the system. When you enter the SET PROCESS/SUSPEND=KERNEL/ID= command in a cluster environment, the KERNEL keyword is ignored if the target process and the current process reside on different cluster nodes. As a result, process suspension is handled as if you had specified the SUPERVISOR keyword (the default). Note that you can specify SET PROCESS/SUSPEND=KERNEL to override a previous SET PROCESS/SUSPEND=SUPERVISOR. SET PROCESS/SUSPEND=SUPERVISOR does not, however, override SET PROCESS/SUSPEND=KERNEL.