3.5.1 Job Attributes/Flags Overview
3.5.1-A Job Attributes
| FLAGS |
| Format: |
<FLAG>[:<FLAG>]... |
| Default: |
--- |
| Description: |
Specifies job specific flags. |
| Example: |
The job can be restarted and should only utilize reserved resources.
|
| PLIST* |
| Format: |
<PARTITION_NAME>[^|&]
[:<PARTITION_NAME>[^|&]]...
|
| Default: |
[ALL]
|
| Description: |
Specifies the list of partitions the object can access. If no
partition list is specified, the object is granted default access to all
partitions. |
| Example: |
The object can access resources located in the OldSP, Cluster1,
and/or O3K partitions.
|
| QDEF |
| Format: |
<QOS_NAME> |
| Default: |
[DEFAULT] |
| Description: |
Specifies the default QoS associated with the object. |
| Example: |
The object is assigned the default QoS premium.
|
| QLIST* |
| Format: |
<QOS_NAME>[^|&]
[:<QOS_NAME>[^|&]]... |
| Default: |
<QDEF> |
| Description: |
Specifies the list of QoSes the object can access. If no QoS
list is specified, the object is granted access only to its default partition. |
| Example: |
QLIST=premium:express:bottomfeeder
The object can access any of the 3 QoSes listed.
|
By default, jobs may access QoSes 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 QoSes 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 ANDed 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.
3.5.1-B Job Flags
| ADVRES |
| Format: |
ADVRES[:<RESID>] |
| Default: |
Use available resources where ever found, whether inside a reservation
or not. |
| Description: |
Specifies the job may only utilize accessible, reserved resources.
If <RESID> is specified, only resources in the specified reservation
may be utilized. |
| Example: |
The job may only utilize resources located in the META.1 reservation.
|
| ARRAYJOBPARLOCK |
| Format: |
--- |
| Default: |
--- |
| Description: |
Specifies that the job array being submitted should not span across multiple partitions. This locks all sub jobs of the array to a single partition. If you want to lock all job arrays to a single partition, specify the ARRAYJOBPARLOCK parameter in moab.cfg to force this behavior on a global scale. |
| Example: |
> msub -t moab.[1-5]%3 -l walltime=30,flags=arrayjobparlock
|
| ARRAYJOBPARSPAN |
| Format: |
--- |
| Default: |
--- |
| Description: |
Specifies that the job array being submitted should span across multiple partitions. This is the default behavior in Moab, unless the ARRAYJOBPARLOCK parameter is specified in moab.cfg. This job flag overrides the ARRAYJOBPARLOCK parameter so that job arrays can be allowed to span multiple partitions at submit time. |
| Example: |
> msub -t moab.[1-5]%3 -l walltime=30,flags=arrayjobparspan
|
| GRESONLY |
| Format: |
GRESONLY |
| Default: |
False |
| Description: |
Uses no compute resources such as processors, memory, and so forth; uses only generic resources. |
| Example: |
> msub -l gres=matlab,walltime=300
|
| IGNIDLEJOBRSV |
| Format: |
IGNIDLEJOBRSV |
| Default: |
N/A |
| Description: |
Only applies to QoS. IGNIDLEJOBRSV allows jobs to start without a guaranteed walltime. Instead, it overlaps the idle reservations of real jobs and is preempted 2 minutes before the real job starts. |
| Example: |
QOSCFG[standby] JOBFLAGS=IGNIDLEJOBRSV
|
| NOQUEUE |
| Format: |
NOQUEUE |
| Default: |
Jobs remain queued until they are able to run. |
| Description: |
Specifies that the job should be removed it is unable to allocate
resources and start execution immediately. |
| Example: |
The job should be removed unless it can start running at submit time.
This functionality is identical to the resource manager extension QUEUEJOB:FALSE.
|
| NORMSTART |
| Format: |
NORMSTART |
| Default: |
Moab passes jobs to a resource manager to schedule. |
| Description: |
Specifies that the job is an internal system job and will not be started via an RM. |
| Example: |
The job begins running in Moab without a corresponding RM job.
|
| PREEMPTEE |
| Format: |
PREEMPTEE |
| Default: |
Jobs may not be preempted by other jobs |
| Description: |
Specifies that the job may be preempted by other jobs which have the PREEMPTOR flag set. |
| Example: |
The job may be preempted by other jobs which have the PREEMPTOR
flag set.
|
| PREEMPTOR |
| Format: |
PREEMPTOR |
| Default: |
Jobs may not preempt other jobs |
| Description: |
Specifies that the job may preempt other jobs which have the PREEMPTEE flag set. |
| Example: |
The job may preempt other jobs which have the PREEMPTEE
flag set.
|
| RESTARTABLE |
| Format: |
RESTARTABLE |
| Default: |
Jobs may not be restarted if preempted. |
| Description: |
Specifies jobs can be requeued and later restarted if preempted. |
| Example: |
The associated job can be preempted and restarted at a later date.
|
| SUSPENDABLE |
| Format: |
SUSPENDABLE |
| Default: |
Jobs may not be suspended if preempted. |
| Description: |
Specifies jobs can be suspended and later resumed if preempted. |
| Example: |
The associated job can be suspended and resumed at a later date.
|
| SYSTEMJOB |
| Format: |
SYSTEMJOB |
| Default: |
N/A |
| Description: |
Creates an internal system job that does not require resources. |
| Example: |
|
| WIDERSVSEARCHALGO |
| Format: |
<BOOLEAN> |
| Default: |
--- |
| Description: |
When Moab is determining when and where a job can run, it either searches for the most resources or the longest range of resources. In almost all cases searching for the longest range is ideal and returns the soonest starttime. In some rare cases, however, a particular job may need to search for the most resources. In those cases this flag can be used to have the job find the soonest starttime. The flag can be specified at submit time, or you can use mjobctl -m to modify the job after it has been submitted. See the RSVSEARCHALGO parameter. |
| Example: |
> msub -l flags=widersvsearchalgo
> mjobctl -m flags+=widersvsearchalgo job.1
|
Related topics