... Greg wrote ...
> > In the mean time, I 
> > will probably rewrite some jobs to STREAM SOMEJOBA.GROUP
> > PAUSE JOB=!HPLASTJOB
> > STREAM SOMEJOBB.GROUP
> > PAUSE JOB=!HPLASTJOB

This approach is fine.  It uses more resources than using a separate job
queue with a job limit of 1 simply because the PAUSE command polls the
JMAT every so often to see if the target job exists.  Another potential
issue is that the pause time could be long of the job limit is less than
what is needed for the next job to run.

...
> The only issues I can think of are resource 
> utilization (which I assume to be minimal), adjusting limits 
> where and how needed, and of course the herculean task of 
> editing those few jobs that must run exclusively. OK, one 
> other issue just now occurs to me: jobs that do not 
> themselves run exclusively, but which should not run while 
> other single-threaded jobs are running....

There is a STREAM UDC on Jazz at:

http://jazz.external.hp.com/src/scripts/stream.txt

which might help.  It maps certain jobs to certain job queues based on
the job name, or user name or account name, etc. Wildcarding is
permitted. The goal is to make it easier for a system manager to move
their jobs to certain job queues without needing to modify either the
job "card" or the STREAM command which invokes the job. 

Hope this helps,
 Jeff Vance, vCSY

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *