It's very similar under DQS (also aims for Posix batch system compliance).
#? is the in-job DQS flag delimiter. -l to specify resources. Other than
qty most resources are sysadmin-defined in queue complexes (qconf -ac
complexname) and then associated with real queues (qconf -cq/-mq).
Some examples in the DQS qsub manpage:
# I want 6 or more machines of group ibm
# with memory greater than 128M, that has pvm
#$ -l qty.gt.6,mem.gt.128,group.eq.ibm,pvm
# If I can get it, I would also like 1 machine
# with memory greater than 256M of group dec
#$ -soft -l qty.eq.1,mem.gt.256,group.eq.dec
Resource flags may use either Fortran or C-like operators for comparison.
Our group has a small cluster with 4 completely distinct architectures, 3
different operating systems, and differing memory and processor
counts/speeds on nearly every node. Major application software (licensed or
otherwise available on only some machines) are listed in the queue complexes
allowing users to specify required programs as just another resource. Most
jobs here are serial or embarrasingly parallel, so the inconvenience of load
balancing heterogenous sets of machines isn't an issue. Homogenous subsets
could be selected using resources limits if necessary.
The nodes assigned to a job are listed in a file pointed to by the
HOSTS_FILE environment variable. A PVM virtual machine may also be set up
for the job by DQS if an appropriate flag is set (-par PVM), though there
are some difficulties if interactive jobs or multiple jobs for the same user
on the same nodes are also setting up PVMs.
-Drake
_______________________________________________
Beowulf mailing list
Beo...@beowulf.org
http://www.beowulf.org/mailman/listinfo/beowulf