At 04:12 PM 15/1/96 -0800, Stan Sieler wrote:
[example deleted....]
>In summary, this is *important* : You need to be able to change the queue
>of an existing job!
 
I respectfully disagree.  A similar situation could be described for output
print queues, that is, a need to be able to change the queue of a printing
spoolfile.  But the fact of the matter is that when the spoolfile is
printing IT IS NO LONGER IN THE QUEUE!  I believe the same view to be true
about the job queues:  when a job is executing it is not in the queue - it
is simply denying the resource for the others in the queue.
 
Besides there must have been a reason in your example to put the big job in
the SINGLETHREAD QUEUE, such as that nothing else is to run - in particular
the 237 other jobs that came after it!  Otherwise, why not run the big job
from another queue?
 
Perhas the best solution then is to have a command to allow you to easily
move the waiting jobs to another queue.
 
Cheers.
----
Jim "seMPEr" Wowchuk
Vanguard Computer Services     Internet:    [log in to unmask]
 _--_|\                        Compu$erve:  100036,106
/      \                       Post:        PO Box 18, North Ryde, NSW 2113
\.--.__/ <---Sydney NSW        Phone:       +61 (2) 888-9688
      v      Australia         Fax:         +61 (2) 888-3056