Neil writes:

> The only thing you are doing is dropping it down a queue and insuring that
>  the program in question executes at that queue. I don't see how there could
>  be problems.

Yes. I was going to write the same thing, but Neil beat me to it. 

In fact, running your reports out of the D-queue is probably the ideal 
situation. C-queue processes should be reserved for the human on-line users. Doing 
this will give the human users the impression of a very responsive machine, and 
yet will have almost no impact on the report generating programs operating 
out of the D-queue, so long as there aren't too many (or any other) jobs running 
during the daytime. 

If you constrain your jobs (which are in the D-queue by default) to the 
evenings and nights, human-run reports in the D-queue will run only very slightly 
longer than they would in the C-queue, but will give the impression to your 
C-queue users that the machine is quite responsive. 

In fact, if you do want to run jobs during the daytime, I would recommend 
that they be run in the E-queue, so that they don't interfere with the D-queue 
human-run reports.

MPE was set up magnificiently for this kind queue specialization. 

My recommendations for the type of processes that should go in each queue are:

     C: human interactive processes (tellers, data entry clerks, etc.)
     D: report writers
     E: daytime background jobs

Wirt Atmar

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