Job Attributes/Flags Overview
||specifies job specific flags
(The job should only utilize reserved resources and should only use
resources on hosts which can be exclusively dedicated)
||specifies the default partition associated with the object.
(The object is assigned the default partition P1)
||specifies the list of partitions the object can access. If no
partition list is specified, the object is granted default access to all
(The object can access resources located in the OldSP, Cluster1,
and/or O3K partitions)
||specifies the default QOS associated with the object.
(The object is assigned the default QOS premium)
||specifies the list of QoS's the object can access. If no QOS
list is specified, the object is granted access only to its default partition/
(The object can access any of the 3 QOS's listed)
*NOTE: By default, jobs may access QOS's based on the 'logical
or' of the access lists associated with all job credentials. For
example, a job associated with user John, group staff, and
class batch may utilize QOS's accessible by any of the individual
credentials. Thus the job's QOS access list, or QLIST, equals the
'or' of the user, group, and class QLIST's. (i.e., JOBQLIST = USERQLIST
| GROUPQLIST | CLASSQLIST). If the ampersand symbol,
'&', is associated with any list, this list is logically and'd with
the other lists. If the carat symbol, '^', is associated
with any object QLIST, this list is exclusively set, regardless of other
object access lists using the following order of precedence user, group,
account, QOS, and class. These special symbols affect the behavior
of both QOS and partition access lists.
||Use available resources where ever found, whether inside a reservation
||specifies the job may only utilize accessible, reserved resources.
If <RESID> is specified, only resources in the specified reservation
may be utilized.
(The job may only utilize resources located in the META.1 reservation)
||Use resources according to the global NODEACCESSPOLICY
||specifies that the job should not share node resources with tasks from
any other job
(The job will only allocate resources from nodes which can be exclusively
dedicated to this job)
|The job may utilize any available resource regardless of hostname
||specifies the list of hosts which should be used by the job.
If more hosts are specified than are needed to meet the jobs total task
requirements, Maui will select needed hosts from the list. If fewer
hosts are specified than are needed to meet the job's total task requirements,
Maui will select all listed hosts and attempt to locate additional resources
(Maui will allocate resources using the specified hosts)
||Jobs remain queued until the are able to run
||specifies that the job should be removed it is is unable to allocate
resources and start execution immediately.
(The job should be removed unless it can start running at submit time.)
||Jobs may not be preempted by other jobs
||Specifies that the job may be preempted by other jobs which have the
PREEMPTOR flag set.
(The job may be preempted by other jobs which have the 'PREEMPTOR'
||Jobs may not preempt other jobs
||Specifies that the job may preempt other jobs which have the PREEMPTEE
(The job may preempt other jobs which have the 'PREEMPTEE' flag
||Jobs are started only after the first scheduling iteration
||NOTE: used only in simulation mode to pre-populate a system.
||Jobs may not be restarted if preempted.
||Specifies jobs can be 'requeued' and later restarted if preempted
(The associated job can be preempted and restarted at a later date)
||Jobs may only access resources within a single partition
||Allows jobs to utilize resources from multiple partitions simultaneously
(The job can be allocated and utilize resources from more than one accessible