Distribute jobs that come in to be processed after Prime time
(Prime=QuietNO) are placed in HOLD status in LISTSERV's reader.
 
When the next job comes in with Prime=QuietNo, the job is placed
into HOLD.  This job is now ahead of the previously held job.
 
This processed for each subsequent job that comes in with Prime=QuietNo.
 
This builds up a queue of jobs to be processed, with the oldest job
at the bottom.
 
I have not paid attention to how Listserv handles these jobs when
Prime time is over.
 
Does LISTSERV ORDER the queue to get the oldest job back at the top?
 
If not, why not?