1 02/06/85  cancel_abs_request, car
 2 
 3 Syntax as a command:  car request_identifiers {-control_args}
 4 
 5 
 6 Function: allows you to delete a request for an absentee computation
 7 that is no longer needed.
 8 
 9 
10 Arguments:
11    you can chose request_identifiers from the following:
12 path
13    is the full or relative pathname for the absentee input segment of
14    requests to be canceled.  You can use the star convention.
15 -entry STR, -et STR
16    identifies requests to be canceled by STR, the entryname portion of
17    the absentee input segment pathname.  You can use the star
18    convention.
19 -id ID
20    identifies one or more requests to be canceled by request
21    identifier.  You can give this identifier to further define any path
22    or -entry identifier (see "Notes").
23 
24 
25 Control arguments:
26 -all, -a
27    searches all priority queues for the specified request type starting
28    with the highest priority queue and ending with the lowest.  It is
29    incompatible with -queue.
30 -brief, -bf
31    suppresses messages telling that a particular request identifier was
32    not found or that requests were canceled when using star names or
33    -all.
34 -foreground, -fg
35    specifies that the foreground absentee queue contains the request(s)
36    to be canceled.
37 
38 
39 -queue N, -q N
40    specifies that queue N of the request type contains the requests to
41    be canceled, where N is a decimal integer specifying the number of
42    the queue.  If you omit it, all the queues are searched.
43 -sender STR
44    specifies that only requests from sender STR should be canceled.
45    You must also give one or more request identifiers.  In most cases
46    the sender is an RJE station identifier.
47 -user User_id
48    specifies the name of the submitter of the request to be canceled if
49    it is not the same as the group identifier of the process.  You can
50    give the User_id as Person_id.Project_id, Person_id, or .Project_id.
51    Both r and d extended access to the queue are required.  This
52    control argument is primarily for operators and administrators.
53 
54 
55 Access required: You need o extended access to the queue to cancel
56 your own request and r and d extended access to cancel somebody else's
57 request.
58 
59 
60 Notes: If you supply -id, only one path or -entry is allowed.  If you
61 give -id in addition to a path or -entry, they must match the same
62 request.  If you provide any path or -entry STR request identifiers,
63 only one -id ID request identifier is accepted and it must match any
64 requests selected by path or entryname.
65 
66 You can supply multiple -id ID identifiers in a single command
67 invocation only if you give no path or entry request identifiers.  The
68 -queue, -foreground, and -all control arguments are mutually
69 incompatible.
70 
71 Normally, deletion can be made only by the user who originated the
72 request.
73 
74 
75 When star names are not used and a single request identifier matches
76 more than one request in the queue(s) searched, none of the requests
77 are canceled.  However, a message is printed telling how many matching
78 requests there are.
79 
80 If the absentee process has already logged in, the user is given the
81 choice of bumping the job and cancelling the request from the queue, or
82 allowing the job to continue running and remain in the queue.  This
83 allows the user to cancel a running absentee process.  When a running
84 absentee process is canceled by a user or an operator, the message
85 "Process terminated by the system.  The reason will be sent by Multics
86 mail."  will appear in the absentee output segment.