iraf.net

There is no way to specify detailed batch job parameters on the IRAF command
line when a job is submitted. In the "& <queue>", the "<queue>" is passed on
to the SYS$SNDJBCW system service as the string value of the parameter
SJC$_QUEUE, specifing the primary or logical name of the queue to be used.
Nonetheless, you can accomplish what you want, by the simple expedient of
setting up a set of batch queues with various predefined quotas, priorities,
and so on. The recommended minimal set is something like this: fast interactive priority, ~10 min cpu quota max
batch lower priority, larger resource quotas
slow lowest priority, very large resource quotasSince each site is free to define the available set of batch queues, it should
not be too difficult to come up with a finite set which provides the user with
sufficient control over their job.

Bruce - Doug asked me to add the following to my reply about batch jobs ...
If you will be running the IRAF task in the background as well
as interactively, both jobs may be writing to the uparm file simultaneously.
First create the new directory, and then you can reset the interactive job's
uparm with: cl> set uparm = home$newuparm/Suzanne>From tody Tue Jan 19 14:51:28 1988
Received: by lyra.noao (5.51/SAG.7)
id AA15982; Tue, 19 Jan 88 14:51:25 MST
Date: Tue, 19 Jan 88 14:51:25 MST
From: tody (Doug Tody X217)
Message-Id: <8801192151.AA15982@lyra.noao>
To: sjacoby
Subject: batch jobs
Cc: rooke, tody
Status: RRegarding your mail to BB on batch jobs-You should also mention that background jobs sometimes need to be run in a
different uparm, or with mkscript, to avoid concurrency problems on uparm
files and any shared user data files. This can cause subtle problems, and
at present only the user can make sure this doesn't occur.