Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!rutgers!ucla-cs!zen!ucbvax!NCSC.ARPA!vtcf
From: vtcf@NCSC.ARPA (Williams)
Newsgroups: comp.os.vms
Subject: Batch queue control
Message-ID: <8709141308.AA01574@ncsc.ARPA>
Date: Mon, 14-Sep-87 09:08:39 EDT
Article-I.D.: ncsc.8709141308.AA01574
Posted: Mon Sep 14 09:08:39 1987
Date-Received: Tue, 15-Sep-87 06:30:42 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 13

Thanks for the responses to submitting multiple jobs to batch queues. However,
it doesn't really solve my problem. I have a queue with a job_limit of 2, 
and unlimited CPU time.  Most of the time everything's fine.  Every once in
a while, someone submits, say, 3 jobs to this queue.  Each of these jobs
take about 50 CPU hours!  No one else submits a job to this queue until the 
next day, so no one complains until then.  I hate to kill a batch job and lose
all the work, so I usually do the following: 1) decrease the priority of one
of the jobs down to one. 2) Decrease the priority or hold any other jobs
submitted by the first person. 3) Increase the job_limit of the queue by one, 
so that someone else can get some time in.  It would be nice if there was a
way to allow a user only one job per queue.  I thought about setting each 
user's MAXJOBS to 2, which would allow only one interactive and one batch
job, but that seems a little harsh.