11.6 Job Defaults and Per Job Limits
11.6.1 Job Defaults
Job defaults can be specified on a per queue basis. These defaults are specified using the CLASSCFG parameter. The table below show the applicable attributes:
| Attribute | Format | Example |
| DEFAULT.FEATURES | comma delimited list of node features | CLASSCFG[batch] DEFAULT.FEATURES=fast,io (jobs submitted to class batch will request nodes features fast and io |
| DEFAULT.WCLIMIT | [[[DD:]HH:]MM:]SS | CLASSCFG[batch] DEFAULT.WCLIMIT=1:00:00 (jobs submitted to class batch will request one hour of walltime by default.) |
11.6.2 Per Job Maximum Limits
Job defaults can be specified on a per queue basis. These defaults are specified using t he CLASSCFG parameter. The table below shows the applicable attributes:
| Attribute | Format | Example |
| MAX.WCLIMIT | [[[DD:]HH:]MM:]SS | CLASSCFG[batch] MAX.WCLIMIT=1:00:00 (jobs submitted to class batch can request no more than one hour of walltime.) |
11.6.3 Per Job Minimum Limits
Furthermore, minimum job defaults can be specified on with the CLASSCFG parameter. The table below shows the applicable attributes:
| Attribute | Format | Example |
| MIN.PROC | <integer> | CLASSCFG[batch] MIN.PROC=10 (jobs submitted to class batch can request no less than ten processors.) |
The Moab Cluster ManagerTM provides an easy to use graphical interface to control job limits.