1 04/11/83  move_imft_request, mir
  2 
  3 Syntax:  mir request_identifiers -control_args
  4 
  5 
  6 Function: moves requests from one Inter-Multics File Transfer (IMFT)
  7 queue to another.  The move can be between queues of the same remote
  8 system or between queues of different remote systems.  The requests are
  9 always placed at the end of the target queue.
 10 
 11 
 12 Arguments:
 13 request_identifiers
 14    determine which requests in the selected queues (-queue/-all/-ds/-sc)
 15    belonging to the specified users (-own/-user) are moved.  See "Notes
 16    on request identifiers" below.
 17 
 18 
 19 List of request_identifiers:
 20 path
 21    moves all requests from the appropriate queues and users whose
 22    source pathnames match the relative pathname path.  The star
 23    convention is allowed.
 24 -entry STR, -et STR
 25    moves all requests from the appropriate queues and users whose
 26    source entry names match STR; the directory portions of the source
 27    pathnames are ignored.  The star convention is allowed.
 28 -id STR
 29    moves all requests from the appropriate queues and users whose
 30    request IDs match the STR.  Type "help request_ids.gi" for a
 31    description of the syntax of STR.
 32 
 33 
 34 Control arguments:
 35 -destination STR, -ds STR
 36    moves requests that are queued for transfer to the remote system
 37    identified by STR.  STR must be one of the names listed by the
 38    print_imft_sites command.
 39 -source STR, -sc STR
 40    moves requests that are queued for transfer from the remote system
 41    identified by STR.  STR must be one of the names listed by the
 42    print_imft_sites command.  If neither -destination nor -source is
 43    specified, the default is -destination imft.
 44 -queue N, -q N
 45    moves requests entered in priority queue N for the above destination
 46    or source where N is an integer between 1 and 4 inclusive.  (Default
 47    -- depends on the destination or source specified)
 48 -all, -a
 49    moves requests entered in all priority queues for the above
 50    destination or source.  If the move is between queues of the same
 51    remote system, the target queue is not searched.
 52 
 53 
 54 -brief, -bf
 55    suppresses messages telling that a particular request identifier did
 56    not match any requests or providing the new request IDs of the moved
 57    requests.
 58 -long, -lg
 59    displays the above messages. (Default)
 60 
 61 
 62 -to_destination STR, -tods STR
 63    specifies that the requests should be moved to the output queues of
 64    the remote system identified by STR.  This control argument cannot
 65    be specified if -source is specified.  (Default -- requests are
 66    moved within the queues of the remote system given by the -ds STR
 67    control argument)
 68 -to_source STR, -tosc STR
 69    specifies that the requests should be moved to the input queues of
 70    the remote system identified by STR.  This control argument cannot
 71    be specified unless -source is also specified.  (Default -- requests
 72    are moved within the queues of the remote system given by the -sc
 73    STR control argument)
 74 -to_queue N, -tq N
 75    specifies that the requests be moved to priority queue N of the
 76    target destination or source where N is an integer between 1 and 4
 77    inclusive.  (Default -- the default queue of the target destination
 78    or source)
 79 
 80 
 81 -own
 82    moves a matching request only if it was submitted by the user of
 83    this command.  (Default)
 84 -user STR
 85    moves a matching request only if it was submitted by the user
 86    identified by STR.
 87 
 88 
 89 List of user specifications:
 90    the STR given to the -user control argument must have one of the
 91    following forms:
 92 Person.Project
 93    moves only those matching requests entered by the specified user
 94    while logged in on the specified project.
 95 Person.*, Person
 96    moves only those matching requests entered by the specified user
 97    while logged in on any project.
 98 *.Project, .Project
 99    moves only those matching requests entered by any user logged in
100    on the specified project.
101 *.*, *
102    moves all matching requests regardless of who entered them.
103 
104 
105 Access required: The user must have at least "a" extended access to the
106 target queue.  If -own (the default) is specified, the user must have
107 at least "o" extended access to the source queues.  If -user is
108 specified, the user must have at least "rd" extended access to the
109 source queues and access to the queue_admin_ gate.  If the user has AIM
110 ring one privelege, the AIM attributes of the original submittor are
111 preserved; otherwise, the AIM attributes of the current process are
112 used.
113 
114 
115 Notes on request identifiers: Multiple -id STR request identifiers may
116 be specified on the command line only if no path or -entry STR
117 identifiers are given.
118 
119 If path or -entry STR request identifiers are given, only one -id STR
120 request identifier may be given in which case only those requests which
121 match one of the path or -entry STR identifiers and which match the
122 -id STR identifier are moved.
123 
124 If a path or -entry STR request identifier matches more than one
125 request and is not a starname, a message is printed telling how many
126 matching requests were found but none of the requests are moved.  The
127 -id STR request identifier may be used to further qualify the path or
128 -entry STR identifier to select the specific request to be moved.
129 
130 
131 Notes: If the request is already being transferred, this command will
132 print a message and refuse to move the request.
133 
134 If conflicting control arguments (eg: -long, -brief) are given on the
135 command line, the rightmost control argument takes effect.