1 03/21/85 next
 2 
 3 Syntax as a command:  next -control_args
 4 
 5 
 6 Function:  specifies which request is to be taken from the queues next.
 7 This allows the operator to specify priority requests and the order in
 8 which they are to be run.
 9 
10 
11 Control arguments:
12 -user Person_id.Project_id
13    specifies the submitter of the request by user_id.  The full person
14    and project names must be given.  This control argument is required.
15    At least one other argument must be chosen from the request
16    identifiers -entry, -path, and -id.
17 -entry STR, -et STR
18    specifies the entryname of the request.  Starnames are not allowed.
19    This control argument may not be used with the -path control
20    argument.
21 -id ID
22    specifies the match id of the request.
23 
24 
25 -path path, -pn path
26    specifies the full pathname of the request.  Relative pathnames and
27    starnames are not allowed.  This control argument may not be used
28    with the -entry control argument.
29 -device STR, -dev STR
30    specifies which of the driver's minor devices the command is being
31    given for.  This control argument is optional for drivers with a
32    single minor device, but is required for drivers with multiple minor
33    devices.  It serves to identify which request type the coordinator
34    will search to find the request.
35 -queue N, -q N
36    specifies that only queue N of the request type should be searched
37    to find a matching request.  This argument is optional; if not
38    given, all queues will be searched.
39 
40 
41 Notes:  All requests to be run by the next command will be charged as
42 though they came from queue 1.
43 
44 Requests chosen to run next will be run after any restarted requests
45 (see the restart command in this section).
46 
47 This command may be given several times before a go command, to specify
48 the exact order that requests in the queues are processed.