Cancels wakeup requests for a specified process, including wakeup
requests scheduled with either the RUN command or the $SCHDWK
system service.
Requires one of the following:
o Ownership of the process.
o GROUP privilege to cancel scheduled wakeup requests for
processes in the same group but not owned by you.
o WORLD privilege to cancel scheduled wakeup requests for any
process in the system.
Format
CANCEL [[node-name::]process-name]
2 Parameters
node-name::
The name of the node on which the specified process is running.
You cannot specify a node name on a different OpenVMS Cluster
system from the current process.
process-name
The name of the process for which wakeup requests are to be
canceled. The process name can have up to 15 alphanumeric
characters.
The specified process must be in the same group as the current
process.
2 Qualifier
/IDENTIFICATION
/IDENTIFICATION=pid
Identifies the process by its process identification (PID). You
can omit leading zeros when you specify the PID.
2 Examples
1.$ CANCEL CALENDAR
The CANCEL command in this example cancels a wakeup request for
a process named CALENDAR (which continues to hibernate until it
is deleted with the STOP command).
2.$ RUN/SCHEDULE=14:00 STATUS
%RUN-S-PROC_ID, identification of created process is 0013012A
.
.
.
$ CANCEL/IDENTIFICATION=13012A
The RUN command in this example creates a process to execute
the image STATUS. The process hibernates and is scheduled to be
awakened at 14:00. Before the process is awakened, the CANCEL
command cancels the wakeup request.
3.$ RUN/PROCESS_NAME=LIBRA/INTERVAL=1:00 LIBRA
%RUN-S-PROC_ID, identification of created process is 00130027
.
.
.
$ CANCEL LIBRA
$ STOP LIBRA
The RUN command in this example creates a subprocess named
LIBRA to execute the image LIBRA.EXE at hourly intervals.
Subsequently, the CANCEL command cancels the wakeup request.
The process continues to exist, but in a state of hibernation,
until the STOP command deletes it.
On this website, Google Analytics is used to track visitor statistics. These are anonymised data about the number of visitors, which pages they visit on this site, from which regions they visit, which web browsers they use, etc.. You will also see non-personalised ads via Google AdSense. Cookies from Paddle or Paypal are placed when you click on a 'Buy now!' or 'Donate!' button, and possible cookies from Disqus when you use that system to comment on one or more blogposts. Privacy Statement