Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mit-eddie!genrad!decvax!ucbvax!XHMEIA.CALTECH.EDU!zar
From: zar@XHMEIA.CALTECH.EDU
Newsgroups: comp.os.vms
Subject: VMS Queue Manipulation
Message-ID: <870423154814.01a@Xhmeia.Caltech.Edu>
Date: Thu, 23-Apr-87 17:48:14 EDT
Article-I.D.: Xhmeia.870423154814.01a
Posted: Thu Apr 23 17:48:14 1987
Date-Received: Sun, 26-Apr-87 21:12:15 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 26

A long time ago, our local management decided that one user could run
only one batch job per queue at a time. At that time I wrote a .COM
file to release the next batch job in sequence submitted with the /HOLD
qualifier. The intention was to design batch jobs as follows:
	$ on error then goto exit
	$ run program
	$ exit: nextjob
then submit jobs with the commands
	$ submit job_1		!First job in sequence
	$ submit/hold job_2	!all jobs in remainder of sequence
	$ submit/hold job_3
	    ...
	$ submit/hold job_n
The NEXTJOB command also took two optional parameters. The first was the
queue to search for jobs. The second was a username (for prived users only)
to release someone elses batch job.

I have since converted the program NEXTJOB to FORTRAN (from .COM and many
MACRO programs). If anyone wants this, send me mail...

					From The Great
					     Zar
					a.k.a. Dan Zirin
					ZAR @ CITCHEM (bitnet)
					ZAR @ XHMEIA.CALTECH.EDU
					XHMEIA::ZAR (span/hepnet)