1 02/18/85  move_output_request, mor
  2 
  3 Syntax as a command:  mor request_identifiers {-control_args}
  4 
  5 
  6 Function: moves a request from one I/O daemon queue to another.  The
  7 move can be within the same request type or from one request type to
  8 another.  The request is always placed at the end of the target queue.
  9 
 10 
 11 Arguments:
 12 request_identifiers
 13    can be chosen from the following:
 14    path
 15       identifies a request to be moved by the full or relative pathname
 16       of the input data segment.  The star convention is allowed.
 17    -entry STR, -et STR
 18       identifies a request to be moved by STR, the entryname portion of
 19       the input data segment pathname.  The star convention is allowed.
 20    -id ID
 21       identifies one or more requests to be moved by request
 22       identifier.  This identifier may be used to further define any
 23       path or -entry identifier (see "Notes").
 24 
 25 
 26 Control arguments:
 27 -all, -a
 28    searches all queues for the requests to be moved.  The target queue
 29    is not searched by -all if the source and target request types are
 30    identical.  This control argument is incompatible with -queue.
 31 -brief, -bf
 32    suppresses messages telling the user that a particular request
 33    identifier was not found or that requests were moved when using star
 34    names or the -all control argument.
 35 -queue N, -q N
 36    specifies that queue N for the given request type contains the
 37    request to be moved, where N is an integer specifying the number for
 38    the queue.  If you omit -queue, all the queues are searched.
 39 
 40 
 41 -print, -pr
 42    specifies that the request moved is found in the queue(s) associated
 43    with the default printer request type (see "Notes").
 44 -punch, -pch
 45    specifies that the request moved is found in the queue(s) associated
 46    with the default punch request type (see "Notes").
 47 -plot
 48    specifies that the request moved is found in the queue(s) associated
 49    with the default plotter request type (see "Notes").
 50 -request_type STR, -rqt STR
 51    specifies that the request moved is found in the queue(s) for the
 52    request type identified by STR.  Use the print_request_types command
 53    to list request types.  (See "Notes.")
 54 
 55 
 56 -to_queue N, -tq N
 57    specifies which queue to move the request to.  If not given, the
 58    default queue of the target request type is used.
 59 -to_request_type STR, -to_rqt STR
 60    specifies that the request should be moved to request type STR.  If
 61    you don't give -to_request_type, the original request type is used.
 62    The target request types must be of the same generic type as the
 63    original request type.
 64 
 65 
 66 -user User_id
 67    specifies the name of the submitter of the requests to be moved.
 68    The User_id can be Person_id.Project_id, Person_id, or .Project_id.
 69    This control argument is primarily for the operator and
 70    administrators.  Both r and d extended access to the queue are
 71    required.  This control argument causes the command to use
 72    privileged message segment primitives that preserve the original
 73    identity of the submitter.  If the process has access isolation
 74    mechanism (AIM) ring 1 privilege, the AIM attributes of the original
 75    submitter are preserved; otherwise the AIM attributes of the current
 76    process are used.  (Default: to move only requests entered by the
 77    user executing the command)
 78 
 79 
 80 Access required: You must have o extended access to the queue from
 81 which the request is being taken and a access to the queue to which the
 82 request is being moved.  You must have r and d extended access to move
 83 a request owned by another user (see -user).
 84 
 85 
 86 Notes: The control arguments -print, -punch, -plot, and -request_type
 87 are mutually exclusive.  If you use none, the default request type for
 88 enter_output_request -print (as displayed by print_request_types) is
 89 assumed.
 90 
 91 If you supply any path or -entry STR request identifiers, only one -id
 92 ID request identifier are accepted and it must match any requests
 93 selected by path or entryname.  You can specify multiple -id ID
 94 identifiers in a single command invocation only if you give no path or
 95 entry request identifiers.
 96 
 97 When you use no star names and a single request identifier matches more
 98 than one request in the queue(s) searched, none of the requests are
 99 moved.  However, a message is printed telling how many matching
100 requests are found.
101 
102 
103 If the request is already running, it is not moved and a message is
104 printed.
105 
106 See the Programmer's Reference Manual for a description of request
107 identifiers.