(Click to open topic with navigation)

You are here: 2 Scheduler Basics > Job Flags

2.8 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:	FLAGS=ADVRES:META.1 The job may only utilize resources located in the META.1 reservation.

ALLPROCS
Format:	---
Default:	---
Description:	Each task should occupy all the processors on the node. Incompatible with ppn and non-Torque systems. ALLPROCS is scheduled to be deprecated in a future Moab version in which it will be replaced with the new NUMA job submission syntax (place=nodes in this particular case).
Example:	msub -l nodes=6 -l flags=allprocs Each of the 6 tasks will occupy all the processors on the node and the job will launch enough processes to occupy each of those processors.

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 if it is unable to allocate resources and start execution immediately.
Example:	FLAGS=NOQUEUE 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:	FLAGS=NORMSTART The job begins running in Moab without a corresponding RM job.

NOVMMIGRATE
Format	NOVMMIGRATE
Default	Moab can migrate the VM associated with the job.
Description	Specifies that Moab may not migrate the VM that the job sets up.
Example	msub -l walltime=INFINITY,template=VMTracking,os=linux,nodes=h3,jobflags=novmmigrate Moab will not migrate the new VM.

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:	FLAGS=PREEMPTEE 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:	FLAGS=PREEMPTOR The job may preempt other jobs which have the PREEMPTEE flag set.

PURGEONSUCCESSONLY
Format	PURGEONSUCCESSONLY
Default	Completed jobs are sent to a queue for a short period of time before Moab purges them from the system.
Description	Specifies that Moab should only purge the job from the completed queue if it completed successfully. If the job failed, Moab will keep it in the queue indefinitely to allow you to restart it at any time. This flag is particularly useful for setup and take down jobs in job workflows. See Creating Workflows with Job Templates for more information.
Example	FLAGS=PURGEONSUCCESSONLY If the job fails, Moab will not purge it from the completed job queue.

RESTARTABLE
Format:	RESTARTABLE
Default:	Jobs may not be restarted if preempted.
Description:	Specifies jobs can be requeued and later restarted if preempted.
Example:	FLAGS=RESTARTABLE 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:	FLAGS=SUSPENDABLE 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:	FLAGS=SYSTEMJOB

USEMOABJOBID
Format	<BOOLEAN>
Default	FALSE
Description	Specifies whether to return the Moab job ID when running "msub", or the resource manager's job ID if it is available. Setting USEMOABJOBID here overrides the global setting for USEMOABJOBID in moabcfg. See USEMOABJOBID for more information.
Example	FLAGS=USEMOABJOBID SELECT=TRUE

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

Setting Per-Credential Job Flags

© 2016 Adaptive Computing