(Click to open topic with navigation)
When creating a job template, you can use any attribute acceptable within the WIKI workload query data format. In addition, job templates can use any of the extension attributes in the following table. Note that the Template type (JMIN, JMAX, JDEF, JSET) row indicates compatibility with the associated attribute (See Applying Templates Based on Job Attributes for more information.).
Attributes set in a template are evaluated as if they were part of the original job submission. Their jobs are still subject to all the same ACLs and policies.
22.6.1 Attributes
CPUCLOCK | |
---|---|
Format | <STRING> |
Template type | JMIN
JMAX JSET |
Description | CPU clock frequency for all CPUs of a job. For more information, see CPUCLOCK. The job template extension overrides the job script. |
Example |
JOBCFG[slow] SELECT=TRUE cpuclock=1400 JOBCFG[fast] SELECT=TRUE cpuclock=3200
JOBCFG[cpu.min] CPUCLOCK=1000 JOBCFG[cpu.max] CPUCLOCK=2000 JOBCFG[cpu.set] CPUCLOCK=1500
JOBMATCHCFG[cpu] JMIN=cpu.min JMAX=cpu.max JSET=cpu.set |
DESCRIPTION | |
---|---|
Format | <STRING> |
Template type | JMAX
JDEF |
Description | Description of the job. When you run the checkjob command, the description appears as Description. |
Example |
JOBCFG[webdb] DESCRIPTION="Template job" |
DPROCS | |
---|---|
Format | <INTEGER> |
Template type | JMIN
JMAX JSET |
Description | Number of processors dedicated per task. The default is 1. |
Example |
JOBCFG[job.min] DPROCS=2
|
ENV | |
---|---|
Format | <STRING> |
Template type | JSET |
Description | Adds the specified job environment variables to the job. |
Example |
JOBCFG[container] ENV=PBS_CONTAINERINFO=centos6 |
EXEC | |
---|---|
Format | <STRING> |
Template type | JSET |
Description | Specifies what the job runs, regardless of what the user set. |
Example |
JOBCFG[setup.pre] EXEC=nfs/tools/setup.pre.sh |
FLAGS | |
---|---|
Format | <JOBFLAG>[,<JOBFLAG>]... |
Template type | JMIN
JDEF JSET |
Description | One or more legal job flag values. |
Example |
JOBCFG[webdb] FLAGS=NORMSTART |
GNAME | |
---|---|
Format | <STRING> |
Template type |
JDEF JSET |
Description | Group credential associated with job. |
Example |
JOBCFG[webserv] GNAME=service For matching the group, see the GROUP attribute. |
GRES | |
---|---|
Format | <genericResource>[:<COUNT>][,<genericResource>[:<COUNT>]]... |
Template type | JMIN
JMAX JDEF |
Description | Consumable generic attributes associated with individual nodes or the special pseudo-node global, which provides shared cluster (floating) consumable resources. Use the NODECFG parameter to configure such resources. |
Example |
JOBCFG[gres.set] GRES=abaqus:2 In this example, the gres.set template applies two Abaqus licenses per task to a matched job. |
GROUP | |
---|---|
Format | <GROUP>[,<GROUP>]... |
Template type | JMIN |
Description | Group credentials associated with job. This is used for job template matching. |
Example |
JOBCFG[webserv] GROUP=service For information about setting the group, see the GNAME attribute. |
MEM | |
---|---|
Format | <INTEGER> |
Template type | JMIN
JMAX JDEF JSET |
Description | Maximum amount of physical memory per task used by the job in megabytes. You can optionally specify other units with your integer (300kb or 2gb, for example). See Requesting Resources in the Torque 6.0.1 Administrator Guide for more information. |
Example |
JOBCFG[smalljobs] MEM=25 |
NODEACCESSPOLICY | |
---|---|
Format | One of the following: SHARED, SHAREDONLY, SINGLEJOB, SINGLETASK , SINGLEUSER, or UNIQUEUSER |
Template type | JDEF
JSET |
Description | Specifies how node resources will be shared by a job. See the Node Access Policies for more information. |
Example |
JOBCFG[serverapp] NODEACCESSPOLICY=SINGLEJOB |
NODERANGE | |
---|---|
Format | <MIN>[,<MAX>] |
Template type | JMAX
JDEF |
Description | Minimum and maximum nodes allowed to be allocated to job. |
Example |
JOBCFG[vizserver] NODERANGE=1,16 |
NODES | |
---|---|
Format | <INTEGER> |
Template type | JMIN
JMAX JSET |
Description |
Number of nodes required by the job. The default is 1. See Node Definition for more information. When using JSET:
|
Example |
JOBCFG[job.min] NODES=2
|
NODESET | |
---|---|
Format | <STRING> |
Template type | JSET |
Description | See Node Set Overview for more information. |
Example |
JOBCFG[medium.set] NODESET=ONEOF:FEATURE:fast,slow |
PARTITION | |
---|---|
Format | <PARTITION>[:<PARTITION>]... |
Template type | JMIN
JDEF JSET |
Description | Specifies the partition (or partitions) in which a job must run. |
Example |
JOBCFG[meis] PARTITION=math:geology |
PREF | |
---|---|
Format | <FEATURE>[,<FEATURE>]... |
Template type | JDEF
JSET |
Description | Specifies which node features are preferred by the job and should be allocated if available. See PREF for more information. |
Example |
JOBCFG[meis] PREF=bigmem |
PRIORITYF | |
---|---|
Format | PRIORITYF='<VALUE>' |
Template type | JSET |
Description |
Applicable only when using NODEALLOCATIONPOLICY with the PRIORITY format. Lets you change the priority function used to allocate nodes for the job. See Node Allocation Policies for available PRIORITY values. |
Example |
JOBCFG[limit.set] PRIORITYF='NODEINDEX' |
PROCRANGE | |
---|---|
Format | <MIN>[,<MAX>] |
Template type | JDEF JSET |
Description | Minimum and maximum processors allowed to be allocated to job. |
Example |
JOBCFG[meis] PROCRANGE=2,64 |
RARCH | |
---|---|
Format | <STRING> |
Template type | JSET |
Description | Architecture required by job. |
Example |
JOBCFG[servapp] RARCH=i386 |
RFEATURES | |
---|---|
Format | <FEATURE>[,<FEATURE>]... |
Template type | JMIN
JDEF JSET |
Description | List of features required by job. |
Example |
JOBCFG[servapp] RFEATURES=fast,bigmem |
RM | |
---|---|
Format | <STRING> |
Template type | JDEF
JSET |
Description | Destination resource manager to be associated with job. |
Example |
JOBCFG[webdb] RM=slurm |
ROPSYS | |
---|---|
Format | <STRING> |
Template type | JDEF
JSET |
Description | Operating system required by job. |
Example |
JOBCFG[test.set] ROPSYS=windows |
SELECT | |
---|---|
Format | <BOOLEAN> : TRUE | FALSE |
Description | Job template can be directly requested by job at submission. |
Example |
JOBCFG[servapp] SELECT=TRUE |
SOFTWARE | |
---|---|
Format | <RESTYPE>[{+|:}<COUNT>][@<TIMEFRAME>] |
Template type | JDEF
JSET |
Description | Indicates generic resources required by the job. See SOFTWARE for more information. |
Example |
JOBCFG[servapp] SOFTWARE=matlab:2 |
TASKS | |
---|---|
Format | <INTEGER> |
Template type | JMIN
JMAX JSET |
Description | Number of tasks required by job. The default is 1. See Task Definition for more information. |
Example |
JOBCFG[job.min] TASKS=4
|
TEMPLATEDEPEND | |
---|---|
Format | <TYPE>:<TEMPLATE_NAME> |
Description |
Create another job from the <TEMPLATE_NAME> job template, on which any jobs using this template will depend. This is used for dynamically creating workflows. See Job Dependencies for more information. SYNCWITH only supports one dependency with Torque as the resource manager. |
Example |
JOBCFG[engineering] TEMPLATEDEPEND=AFTER:setup.pre
|
UNAME | |
---|---|
Format | <STRING> |
Default |
JDEF JSET |
Description | User credential associated with job. |
Example |
JOBCFG[webserv] UNAME=service For matching the user, see the USER attribute. |
USER | |
---|---|
Format | <USER>[,<USER>]... |
Template type | JMIN
JMAX |
Description | User credentials associated with job. |
Example |
JOBCFG[webserv] USER=service For setting the user, see the UNAME attribute. |
Related Topics